Search SkillsMP Skills

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds a 'Returns' section outlining the output fields (name, description, author, star count), which is useful given there is no output schema. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with separate sections for args, returns, and examples, making it easy to scan. It repeats some schema information, but this is acceptable for completeness and does not make it excessively long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity and lack of an output schema, the description covers all necessary aspects: purpose, when to use, parameters, return structure, and examples. It is complete enough for an agent to select and invoke the tool appropriately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides thorough descriptions for all parameters (100% coverage). The description enhances the 'query' parameter with concrete examples that illustrate intended usage, though page, limit, and sortBy only repeat the schema's existing descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches for AI skills using keywords from the SkillsMP marketplace, providing a specific verb and resource. It includes concrete examples like 'PDF manipulation' and 'web scraper', but it does not differentiate from the sibling tool 'skillsmp_ai_search_skills'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes an explicit instruction to use this tool before starting any task to check for existing skills, which is strong usage guidance. However, it does not mention when not to use it or compare with the sibling search tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.