Cache Clear

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

No annotations are supplied, so the description carries the full burden. It implies invalidation via 'clear' but says nothing about whether the action is destructive or reversible, what permissions are required, or what happens when the optional bins argument is omitted (default null) – a materially ambiguous outcome for a cache tool.

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?

A single front-loaded sentence with no filler, but its brevity reflects under-specification rather than tight communication. It is efficient but leaves key operational details unstated.

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 mutating cache operation with no annotations and an ambiguous optional parameter, this is too thin. Although an output schema exists to explain returns, the description still omits destructive/permision context and the behavior when no bins are provided.

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 description coverage is 0% for the single 'bins' parameter. The description only echoes the parameter name and adds no format, allowed bin names, or default-omission behavior, so it does not compensate for the undocumented 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?

States a specific verb (Clear) and resource (cache bins), so the agent knows the operation. It does not, however, distinguish itself from the closely-named sibling cache_rebuild or explain what a 'bin' is, leaving the agent to infer the difference.

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 when-to-use guidance, no preconditions, and no mention of the alternative cache_rebuild. The sentence implies only that clearing is possible, not when an agent should prefer it over a full rebuild.

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