search_dictionary

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

With no annotations provided, the description carries the full burden. It reveals a result limit of 10 and that query matches against names, definitions, and tags. However, it does not disclose error behavior, authentication needs, or any potential side effects. This is adequate but not comprehensive.

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, with a clear introductory sentence and a separate section listing arguments. No unnecessary words or repetition.

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 the presence of an output schema (not shown) and no annotations, the description covers the core functionality: search behavior, parameter details, and result limit. It omits details like pagination or error conditions, but for a simple search tool this is sufficient.

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?

Since schema coverage is 0%, the description compensates well by explaining that 'query' matches against multiple fields and 'tag' is an optional filter with examples. This adds meaning beyond the basic type information in the 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 it searches the AI Dictionary by keyword, with an optional tag filter. It specifies the resource and action, and mentions returning up to 10 terms. However, it does not explicitly differentiate from siblings like lookup_term, though the search vs lookup distinction is implicit.

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 gives no guidance on when to use this tool versus alternatives such as lookup_term or propose_term. There is no mention of use cases, prerequisites, or exclusion criteria, leaving the agent to infer from context.

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