Guidelines for naming MCP tools, describing parameters, and documenting tools in a language- and framework-agnostic manner
97
Pending
Does it follow best practices?
Impact
97%
1.02xAverage score across 5 eval scenarios
Pending
The risk profile of this skill
Tool naming conventions and structure
snake_case formatting
100%
100%
Domain prefixes
100%
100%
Action-oriented verbs
100%
100%
Naming consistency
100%
100%
Predictable patterns
100%
100%
Discoverable grouping
100%
100%
Parameter documentation and type definitions
Generic type names
100%
100%
Constraint documentation
93%
93%
Example values
100%
100%
Unit specification
100%
66%
Validation rules
100%
91%
Default values
100%
100%
Error messages
20%
100%
Valid/invalid examples
50%
50%
Cross-tool consistency and organization
Consistent parameter names
100%
100%
Parameter ordering
86%
100%
Documentation structure
100%
100%
Error format
100%
100%
Tool grouping
100%
100%
Tool index/categorization
80%
100%
Cross-references
100%
100%
Tool documentation structure and error handling
Avoid implementation details
100%
100%
Document behavior, not implementation
100%
100%
Consistent documentation structure
100%
100%
Error format consistency
100%
100%
Cross-platform considerations
100%
100%
See also references
100%
100%
Tool dependencies
100%
83%
Active voice
87%
87%
One-liner descriptions
66%
100%
Output contract clarity
100%
100%
Comprehensive tool definition and guideline application
Naming convention violations
100%
100%
Parameter type issues
100%
100%
Missing constraints/examples
100%
100%
Implementation details in docs
100%
100%
Error documentation
100%
100%
Documentation structure
100%
100%
Cross-tool consistency
100%
100%
Tool organization
77%
100%
Language-agnostic practices
100%
100%
Side effects documentation
100%
100%
Failure mode details
100%
100%