clear_snapshot

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

No annotations are provided, so the description carries full burden. It only states 'Clear snapshot cache' without disclosing side effects, what the cache contains, whether the action is reversible, or any permission requirements. This is insufficient behavioral disclosure for a destructive-like operation.

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 with two short sentences. Every word earns its place, conveying the action and usage frequency without any 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?

The tool is simple with no parameters and no output schema, so the description covers the basic purpose. However, it lacks any behavioral details (e.g., effect on other components, whether it clears across sessions) that would help an agent understand the full impact. It is minimally adequate but has clear gaps.

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 input schema has zero parameters with 100% coverage (empty). The description adds minimal meaning beyond the schema by characterizing the action as clearing a cache and noting it's usually not needed. Given the baseline of 4 for zero parameters, the description provides adequate context.

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 'Clear snapshot cache' uses a specific verb and resource, clearly stating the tool's action. The name 'clear_snapshot' aligns directly with the description. There is no sibling tool with a similar purpose, so differentiation is unnecessary.

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 adds 'Usually not needed,' which implies infrequent use, but provides no explicit guidance on when to use this tool, when not to, or alternatives. There is no context about prerequisites or scenarios where clearing the cache is beneficial.

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