clear_entrez_cache

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

No annotations are provided, but the description fully discloses behavior: it clears cache, returns a dictionary with success/cleared count/database cleared/cache location, and notes on caching optionality, TTL, and storage.

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?

The description is well-structured with sections (Args, Returns, Examples, Notes) and front-loaded purpose. While slightly lengthy, each section provides value; minor conciseness improvements possible.

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 covers all necessary aspects: purpose, parameters, return values (despite output schema presence), examples, and behavioral notes. No gaps remain for a simple one-parameter tool.

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 single parameter 'database' is explained: 'Database name to clear (empty string clears all databases)'. Examples illustrate usage. This adds significant meaning beyond the schema's default type.

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 clearly states 'Clear cached Entrez results' and explains the caching system. It uniquely identifies the tool's purpose among siblings, none of which deal with cache clearing.

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 description advises using the tool to clear stale cache data and provides notes on caching behavior, but lacks explicit when-to-use vs. alternatives. However, no alternatives exist for cache clearing.

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