search

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

The description only states it searches by keyword but provides no information about the return format, pagination, scope, or any limitations. No annotations exist to compensate.

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 short, but the bilingual repetition adds redundancy. The structure is simple, but it wastes space with translation that may not be needed for an English-speaking AI agent.

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 does not specify the output or the scope of the search. It does not indicate whether it searches across all servers or within a context. The presence of 'discover' as a sibling suggests another search-like tool, but no differentiation is provided.

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 description merely repeats the parameter name 'query' and provides a redundant translation. It does not specify format, allowed values, or examples. Schema coverage is 0%, but the description fails to compensate.

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 specifies the verb 'search', the resource 'indexed server cards', and lists the fields searched (name, description, categories, tool names). This provides a clear purpose, though it does not explicitly contrast with sibling tools like 'discover'.

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 lacks any guidance on when to use this tool versus alternatives, such as when to use 'discover' instead. It does not specify prerequisites or exclusions.

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