dictionary_suggest

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

Description mentions offline source and ordering but lacks disclosure about read-only nature, latency, or return format. Without annotations, more behavioral context (e.g., 'no modifications made') would improve transparency.

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?

Single sentence, concise and front-loaded with key information. No unnecessary words 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?

For a simple 2-parameter tool with no output schema, the description covers purpose, source, and ordering. However, omitting return format and limit details prevents full completeness.

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 has 0% description coverage, so description must compensate. It clarifies that 'prefix' is a partial word and hints at ordering, but does not explain 'limit' beyond its schema constraints. Adding 'maximum number of suggestions' would raise score.

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?

Description clearly states the tool provides autocomplete suggestions for a partial English word, specifying the data source (offline CMU dict) and ordering (shortest matches first). This distinguishes it from sibling tools like dictionary_lookup or dictionary_search.

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 alternatives. With many sibling tools, the description should at least hint at use cases (e.g., 'for autocomplete when typing') or mention when not to use it (e.g., 'not for exact word lookup').

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