clear_snapshot

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

No annotations are provided, so the description must carry the full burden. It states 'clear snapshot cache' but does not disclose whether this is destructive, irreversible, or has side effects. The agent is left to assume behavior without confirmation or warnings.

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, no unnecessary words. However, it is almost too brief, lacking some details that could improve usefulness without adding verbosity.

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 tool has no parameters, no output schema, and a simple action, the description is minimally adequate. However, it fails to explain what 'snapshot cache' encompasses or confirm that the operation is safe (or dangerous). The sibling 'take_snapshot' provides some context but the description could be more complete.

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?

There are no parameters, so the description does not need to add meaning beyond the schema. Baseline of 4 applies as no parameter information is required.

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 verb 'clear' and resource 'snapshot cache' clearly indicate the action and target. While there is a sibling 'take_snapshot' that suggests a create/clear relationship, the description does not explicitly differentiate, but the purpose is immediately understandable.

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 phrase 'Usually not needed' hints at infrequent use but provides no explicit guidance on when to use the tool, when to avoid it, or what alternatives exist (e.g., 'take_snapshot'). The lack of context or exclusions leaves the agent uncertain about appropriate usage.

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