cache_store

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

The description discloses that the prompt is auto-hashed, which is a behavioral trait beyond the schema. However, it fails to mention behavior on duplicates, overwrites, size limits, or rate limits, and there are no annotations to fill the gap.

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 a single sentence that efficiently conveys the core purpose and key parameters. It is concise and front-loaded, though slightly more structure could improve readability.

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 presence of an output schema, the description does not need to explain return values, but it omits any mention of what the tool returns. It covers input semantics adequately but leaves some behavioral and output context incomplete.

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?

With 0% schema description coverage, the description adds meaning for most parameters: prompt (auto-hashed), result, tokens_saved, ttl_seconds, and metadata. It does not mention client_id, but covers 5 of 6 parameters with useful context.

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 'Store a prompt+result in the cache', using a specific verb and resource. It distinguishes from siblings like 'cache_invalidate' and 'cache_lookup' which perform different operations.

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 guidance is provided on when to use this tool versus alternatives. The description does not include when-to-use, when-not-to-use, or any exclusions.

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