find_synonyms

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

With no annotations, the description mentions data sources (WordNet, corpus) and topic biasing but does not disclose safety (read-only), error handling, or performance characteristics. More context needed for a robust behavioral profile.

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 no filler. Core information is front-loaded, efficient, and easy to scan.

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?

For a simple synonym lookup tool with well-documented schema, the description provides adequate context. Lacks details on return format or edge cases, but these are partially covered by the sibling tool set and the tool's straightforward nature.

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 descriptions cover all parameters (100% coverage), so baseline is 3. The description adds minimal value beyond the schema; 'Optionally bias' repeats schema text. No new parameter meanings are introduced.

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?

Clearly states the tool finds synonyms for a given word, specifying data sources (WordNet and corpus) and an optional topic bias. Distinct from siblings like find_antonyms or find_rhymes.

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?

No explicit guidance on when to use this tool versus siblings such as find_related_words or find_by_pattern. The description implies synonym lookup but does not provide conditions or exclusions.

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