cache

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

With no annotations, the description carries the behavioral burden. It does communicate the basic operation model and even hints at what clearing affects ('stale cached responses'). However, it does not disclose whether 'clear' wipes the entire cache, whether enable/disable persists, or whether any actions are destructive or require privileges.

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 compact and front-loaded: a one-sentence purpose, two concrete use cases, then the parameter details. Every sentence earns its place and there is no redundant or filler content.

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 one-parameter tool with an output schema, the description covers the action values and gives practical usage context. It is nearly complete, but slightly more detail on the side effects of clear/disable/enable would make it fully self-sufficient given the absence of annotations.

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?

Despite 0% schema description coverage, the description fully documents the only parameter: action, its allowed values ('stats' | 'clear' | 'disable' | 'enable'), and its default ('stats'). This adds real meaning beyond the raw schema, which only shows a string with a default.

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 first sentence states the tool's purpose with a specific verb and resource: 'Inspect the response cache' and then enumerates the exact operations supported (stats, clear, enable, disable). This unambiguously separates it from the sibling scraping and search tools, none of which touch the cache.

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 gives clear, actionable use cases: check hit rates before large batch jobs, and clear stale responses after content changes. It does not explicitly mention alternatives or exclusions, but no alternative cache tool exists among the siblings, so the guidance is sufficient.

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