Doppelreim Rhymes

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuine behavior beyond that: results are ranked ('strongest results come first'), language breadth ('50+ languages'), and that classic rhymes are grouped by matching syllables. Only return-shape and rate/limit behavior are unstated, and an output schema exists.

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, front-loaded with the core action, then the discriminating detail for each mode. No filler, no repetition of annotations or schema boilerplate.

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?

With an output schema present, return values need not be described, and the description covers the tricky parameter semantics, ranking, and language scope. The one gap is sibling differentiation against find_rhyming_lines, which an agent would need to resolve elsewhere.

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%, so the baseline is 3, but the description meaningfully expands the enum values beyond the schema's bare 'Kind of rhyme' — explaining double as multisyllabic, classic as perfect end rhymes grouped by syllable, and vowel as assonance. That is the kind of semantic lift the schema does not provide.

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?

States a specific verb and resource ('Find rhymes for a word or short phrase') and even clarifies the semantic variants of 'type'. It does not, however, differentiate itself from the sibling find_rhyming_lines, which remains a plausible alternative for an agent choosing a tool.

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?

Usage is implied by the tool's obvious scope, and 'best for rap and poetry' gives parameter-level guidance, but there is no statement of when to prefer this over find_rhyming_lines or any exclusion. An agent must infer routing from the name alone.

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

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so the safety profile is covered. The description adds useful content context (results are real lyrics, proverbs and sayings rather than generated text), but says nothing about result size, ranking, or how few lines may be returned for uncommon words.

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 tight sentences with the mechanism (what it returns) front-loaded before the motivational use case. No filler, nothing redundant with the schema.

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?

An output schema exists, so return structure need not be explained, and annotations cover the mutation profile. For a one-required-param lookup tool this is nearly sufficient; only the relationship to the find_rhymes sibling is left unstated.

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 description coverage is 100% — word, limit, language and vocabulary all carry their own descriptions, including the supported language list and the rap/general enum distinction. The description adds only the vague phrase "the given word", so 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?

States a specific verb (find) and resource (real lines ending in a rhyme) with illustrative examples of source material. An agent can infer it differs from find_rhymes (which likely returns words), but the sibling is never named, so the distinction rests on inference.

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?

"Useful as inspiration for the next line of a verse" implies the use case but gives no explicit when-to-use/when-not and never mentions find_rhymes as the alternative for a different need. Guidance is implied rather than stated.

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