clear_snapshot

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

The description states the action (clearing a cache) and adds 'Usually not needed' as a usage hint. With readOnlyHint=false, the agent knows it's a mutation, but the description doesn't disclose potential side effects (e.g., whether clearing affects existing snapshots or requires specific conditions). This is minimally transparent.

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 short sentences, front-loaded with the main action and a pragmatic qualifier. Every word earns its place, with no redundancy or filler.

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 simple zero-parameter tool without an output schema, the description covers the core action and a usage hint. However, it doesn't elaborate on what 'snapshot cache' entails, when clearing becomes necessary, or what impacts it has on the broader snapshot workflow, leaving some ambiguity.

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 tool has zero parameters, so the description doesn't need to explain any. Per the baseline for 0-param tools, the score is 4; no additional parameter meaning is needed.

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 the action ('Clear snapshot cache') with a specific verb and resource, distinguishing it from sibling tools like take_snapshot, which creates snapshots. The purpose is unambiguous.

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?

Only guidance is 'Usually not needed,' which hints at rarity but does not explain when the tool should actually be used, what prerequisites exist, or when to avoid it. No explicit context or alternatives are provided.

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