refresh_dictionary

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

Without annotations, the description clearly explains that the tool clears cached data and that subsequent lookups will fetch fresh results. It does not mention if it is safe or destructive, but the action is non-destructive by nature.

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 purpose, and no wasted words. Every sentence adds essential information.

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 tool's simplicity and the presence of an output schema, the description covers all necessary information: what it does, when to use it, and the effect on other tools.

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?

There are no parameters; the description correctly avoids adding parameter details. Baseline for 0 parameters is 4, and no additional information is needed.

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 explicitly states the tool clears cached dictionary data and when to use it, such as after a term proposal is approved. It clearly distinguishes from reading tools like lookup_term and search_dictionary by indicating it ensures fresh results.

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?

Provides specific scenarios: call after a term proposal is approved or whenever fresh data is needed. Lacks explicit when-not-to-use or alternatives, but context is clear enough for typical use.

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