search_skills

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Search skills by keyword' and reveals nothing about return format, pagination, ordering, default limit behavior, or safety (e.g., read-only). This is a minimal explanation that fails to convey any behavioral trail beyond the tool's name.

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 a single, concise sentence: 'Search skills by keyword'. It is front-loaded with the verb and resource, and every word earns its place. No unnecessary information is included.

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?

For a search tool with no output schema and no annotations, the description is too sparse. It does not explain what the search returns, how results are ordered, or how the limit parameter affects results. It also does not clarify when to select this tool over list_skills or get_skill, making it incomplete for an AI agent to use reliably.

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?

Schema description coverage is only 50% (query has a description, limit does not). The description maps to the query parameter but adds no meaning for the limit parameter. Since schema coverage is not high, the description should compensate, but it does not, leaving limit's purpose and default unexplained.

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 action ('Search') and resource ('skills') with a specific method ('by keyword'). This distinguishes it from sibling tools like list_skills and get_skill, making its purpose unmistakable.

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 provides no guidance on when to use this tool versus alternatives such as list_skills or get_skill. It does not mention exclusions or preferred contexts, leaving the agent without explicit decision criteria.

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