ddb_clear_cache

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

The description expands on the annotations by clarifying the scope of cleanup ('cache='spells' clears just the spell/reference compendium; 'all' wipes every cache') and the timing ('cached for up to 5 minutes'). It also notes the effect of forcing an immediate retry. These details add significant context beyond the structured annotation hints.

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 two sentences, front-loading the action and purpose. It then efficiently delivers usage context and parameter details without redundancy. Every clause adds value.

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 tool with one optional parameter and no output schema, the description covers the purpose, when to use it, and the effects of each parameter value, while benefiting from rich annotations. Nothing essential is missing.

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 input schema already has a detailed description for the 'cache' parameter, including enum meanings. The tool description reinforces the default value and gives a practical example of why you'd choose 'spells' vs 'all', but it largely overlaps with the schema's own documentation, adding moderate value.

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 the tool's action ('Wipe in-process caches') and its purpose ('so the next call re-fetches from D&D Beyond'). It also distinguishes this tool from siblings by focusing on cache clearing rather than lookup or navigation, and includes specific scenarios like the SRD/Open5e fallback.

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 provides explicit usage guidance: 'Use this when search results look like the SRD/Open5e fallback...' It gives a concrete trigger with an example and explains the caching duration. However, it does not mention when not to use the tool or compare with alternatives, but none are obvious in the context.

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