prune_cluster

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

No annotations are provided. The description only says 'Move or delete papers,' but the parameters archive and delete (with defaults true and false) suggest 'move' means archiving. It does not explain the effect of archiving, whether it is reversible, or what permissions are needed. The dry_run parameter is not mentioned.

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 (one short sentence), but this comes at the cost of clarity. It omits critical details and does not earn its place by being informative.

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?

With 5 parameters, 0% schema coverage, no annotations, and an existing output schema, the description is severely incomplete. It fails to explain the distinct roles of archive and delete, the purpose of dry_run, or what the tool returns. The agent cannot reliably use this tool based on the description alone.

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%, so the description must compensate, but it only references 'label' without explaining cluster_slug, archive, delete, or dry_run. The description adds no value beyond parameter names, leaving the agent to guess the semantics of each parameter.

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 states 'Move or delete papers with the given label,' which provides a specific verb and resource. However, it does not differentiate from sibling tools like move_paper, remove_paper, or label_paper, nor does it clarify that the action is within the context of a cluster.

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?

No guidance is given on when to use this tool versus alternatives. For example, when should a user use 'prune_cluster' instead of 'move_paper' or 'remove_paper'? The description lacks any context about prerequisites or exclusions.

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