Search terminal tool catalog

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

With no annotations, the description discloses fuzzy matching, offline operation, sync requirement, and return score (0=perfect). It lacks details on error states or behavior if index is missing.

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 with zero waste. The description is front-loaded with the core purpose and adds essential offline/sync context efficiently.

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 no output schema, the description minimally explains return values (score). It could elaborate on result structure or ordering, but it covers key behavioral aspects adequately for the parameter count.

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 coverage is 100%, and the description does not add meaning beyond what the schema already provides for 'query' and 'limit'. The baseline of 3 is appropriate.

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 performs fuzzy searches on the local Terminal Trove catalog by tool name or slug. It distinguishes itself from siblings like 'search_tools' by specifying offline operation after syncing.

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?

It explains the prerequisite (sync_catalog) and the offline nature, guiding when to use. However, it doesn't explicitly mention alternatives or when not to use it, leaving some ambiguity.

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