tg_cache_clear

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

Direct contradiction: annotations declare destructiveHint=false, yet the description says the tool can 'delete everything in data/downloads.' That is destructive behavior, and the contradiction is significant. The idempotentHint=true aligns with cache-clearing, but the annotation conflict forces a score of 1.

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 sentence that front-loads the primary purpose and then states the optional behavior. There is no filler or redundant restatement of the tool name.

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?

The tool is simple with one optional parameter, and the description covers the core behavior. However, the destructive optional operation lacks caveats about permanence or scope, there is no output/return information, and the annotation contradiction makes the description incomplete as a safe guide.

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?

The schema only provides type and default for the 'downloads' parameter, with 0% schema description coverage. The description compensates by tying the parameter to 'optionally delete everything in data/downloads,' which gives an agent the essential meaning, though it could explicitly state 'when true.'

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 states a specific action ('drop the cached chat-title index'), the resource, and the trigger condition ('use after chats are renamed'). It also clearly names the optional secondary effect (delete downloads), making the tool's purpose unambiguous and distinguishable from related index/cache 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?

The description explicitly says when to use the tool ('use after chats are renamed') and gives the condition for the optional downloads deletion. It does not mention when not to use it or name alternatives, but the stated context is clear enough for basic selection.

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