rhymes

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

With no annotations provided, the description carries the full burden, and it delivers meaningful behavior: near means exactly one ARPAbet-token insertion, deletion, or substitution; there is no configurable edit distance; the query is excluded from results. This makes the tool's matching behavior predictable without overclaiming.

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?

Every sentence earns its place: the core purpose, data source, near-mode definition, fixity of edit-distance behavior, and query exclusion are all stated in five short sentences. There is no filler or redundancy.

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 is self-contained for a read-only lookup tool: it explains source, matching semantics, fixity of behavior, and exclusion of the query. The input schema already documents normalization and limit constraints, and an output schema exists, so return-value details are not required here.

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 schema covers text and limit but leaves mode undocumented. The description compensates by defining near precisely and clarifying exact versus near behavior. It also adds CMUdict context that helps interpret text as an English lookup term rather than a free-form phrase.

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 opens with a specific verb and resource: "Find exact or near English rhymes." It goes beyond a generic statement by specifying CMUdict-backed headwords, which clearly distinguishes rhymes from dictionary lookup, synonyms, and semantic-neighbor 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?

The usage intent is implied clearly by the tool name and opening sentence, and the near-mode edit-distance definition gives useful decision context. However, it never explicitly states when to prefer this over sibling tools like dictionary_semantic_neighbors or wordplay, nor does it provide when-not-to-use guidance.

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