search_skillsmp

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explains what is searched and lists parameters with defaults, but it does not mention authentication, rate limits, result behavior, or any side effects. For a read-only search tool, this is adequate but not deeply transparent.

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 concise and well-structured: a single opening sentence followed by a tight argument list. Every line adds value, and the key purpose is front-loaded.

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?

The description covers all parameters with useful examples and defaults, and an output schema exists so return-value details are not required. It is complete for a search tool, though it could briefly reference the sibling fetch tool for completeness.

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 schema has 0% description coverage, but the description fully compensates by documenting all five parameters: q with examples, limit with default and max, sortBy with valid values, category with slug examples, and language with ISO examples. This adds substantial meaning beyond the bare schema.

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 the tool searches the SkillsMP marketplace for skills, workflows, and prompts using keywords. It names the specific resource and action, and the verb 'Searches' distinguishes it from the sibling fetch_skillsmp_skill.

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 implies the tool is for keyword-based discovery, but it does not explicitly mention when to use search versus fetch_skillsmp_skill, nor any exclusions or prerequisites. The usage context is clear but no direct guidance about alternatives is provided.

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