snapshot_switch

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description offers nothing: no statement of side effects, permissions, reversibility, or return behavior. An agent cannot know whether this is a read, write, or destructive 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 short but this is under-specification rather than effective conciseness. It is a single vague phrase that adds no value and fails to address any critical information. It earns a 2 for not being verbose but is far from a well-structured description.

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 6 parameters, no annotations, no output schema, and a complex domain (snapshot management), the description is completely inadequate. An agent cannot safely or correctly invoke this tool. It lacks every piece of context needed for correct usage.

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%, and the description adds no information about any of the 6 parameters. With zero guidance on request_id, snapshot_id, target_commit, etc., an agent has no idea what values are expected or how they relate to the tool's function.

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 'snapshot switch' is a tautology that merely restates the tool name. It provides no verb, resource, or scope. An agent cannot infer what the tool does, what it operates on, or how it differs from sibling tools like snapshot_cleanup or snapshot_catalog.

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 gives no indication of when to use this tool versus any alternative. There is no context, prerequisites, or exclusion criteria. With 80+ sibling tools, an agent has no basis for selection.

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