Update cache

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

Annotations already convey that this tool is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds no behavioral context beyond what annotations provide, such as prerequisites, side effects, or the specific configuration changes that occur.

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 extremely concise but at the cost of utility. A single sentence that merely restates the tool name is under-specified. While short, it does not earn its place by providing useful info beyond the title.

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 complexity of the tool (6 parameters, multiple enums, no output schema), the description is far too minimal. It fails to summarize the modifiable attributes or any relevant context for the cache update operation. The schema descriptions are rich, but the description should integrate those for a complete overview.

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?

Schema coverage is 100%, with each parameter having a description. The tool description does not enhance parameter semantics, but the baseline is 3 because the schema already handles param documentation. No additional value from description.

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 'Update a cache.' clearly indicates the action (update) and resource (cache), but it adds no specificity beyond the tool name. It does not distinguish from sibling tools like create_cache or get_cache, and fails to mention what aspects of the cache can be updated (e.g., size, policy).

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 (e.g., create_cache for new caches, delete_cache for removal). The description does not include any when-not or contextual hints for an agent to decide.

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