snapshot_cleanup

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, permissions, idempotency, or impact on snapshots. The agent has zero information about what happens when the tool is called, whether it is destructive, or what resources it affects.

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 brief but this is under-specification, not conciseness. While it is only two words, it fails to earn its place by providing any actionable information. The lack of structure or front-loaded content means an agent gains nothing from reading it.

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 an 8-parameter tool with no output schema, no annotations, and zero schema coverage, this description is severely incomplete. An agent cannot possibly know what inputs are expected, what the tool does, or what to expect in return. The description is wholly inadequate for any invocation scenario.

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?

With 8 parameters and 0% schema coverage, the description adds no meaning to the parameters. The schema itself provides only names and types with no descriptions. The required parameters 'repository_id', 'actor', and 'permission_scope' are left entirely undocumented, and the description offers zero clarification.

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 cleanup' is a tautology that merely restates the tool name. It does not specify any verb-resource relationship, what is being cleaned, or what the operation entails. With no additional context, an agent cannot distinguish this from any other cleanup operation.

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?

There is no guidance on when to use this tool versus any of the 70+ sibling tools. The description provides no context, prerequisites, or exclusions, leaving the agent completely in the dark about appropriate invocation scenarios.

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