Patch cache

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

Annotations already indicate write (readOnlyHint false) and idempotent. The description adds dryRun behavior and optional gc, but it does not clarify whether the input cache is mutated in place or a new store is returned, which is a behavioral 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?

Two sentences, no fluff, front-loaded with the action and outcome.

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?

Despite having an output schema and annotations, the description is too sparse for a tool with a complex operations structure. It does not explain the operation types (modify/evict) in enough detail to construct valid operations, and the gc behavior is only mentioned as optional.

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 coverage, the description only minimally addresses parameters: it mentions gc and dryRun, but does not explain the 'operations' structure or the 'cache' parameter beyond being a serialized cache. This is insufficient for the complex nested operations schema.

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 identifies the tool as applying declarative repairs (modify/evict, optional gc) to a serialized cache, which is distinct from the sibling diagnostic tools. The verb 'apply' and resource 'cache' are specific, and it mentions the core actions.

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 a clear hint about using dryRun for validation, but it does not explicitly compare with sibling tools or specify when to use this over diagnostic tools. The usage guidance is implied rather than explicit.

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