searchTools

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

Read-only nature is confirmed by annotations (readOnlyHint=true). The description adds search behavior and a recommended workflow, but does not detail output format or limitations beyond the schema.

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?

Two sentences: one states purpose, one gives usage guidelines. No redundant information, perfectly front-loaded for an 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?

While the usage workflow is well explained, the description does not specify the output format (e.g., list of tool names, full details). Without an output schema, this omission leaves ambiguity for the agent about what 'find tools' returns.

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?

All three parameters have descriptions in the input schema (100% coverage). The description adds no new semantic information beyond mentioning 'keyword or category', so baseline 3 applies.

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 finds tools by keyword or category, and positions it as a search alternative to tools/list, which distinguishes it from sibling tools.

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?

Explicitly says to use this before tools/list to avoid loading all schemas, and in --lazy-tools mode, call this first and then tools/schema for full schema. Provides clear context and alternatives.

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