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

With no annotations, the description carries the burden of behavioral disclosure. It goes beyond the basic action by exposing an important postcondition: after purging, reading a dropped version returns not found. It does not mention irreversibility, auth requirements, or rate limits, but the core destructive side effect is clearly conveyed.

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 a single sentence with no filler, and the main action and condition are front-loaded. The postcondition is expressed compactly using the {version: ...} response notation.

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?

For a destructive version-pruning tool with no annotations and no output schema, the description adequately conveys the action, retention condition, and consequence of reading dropped versions. It could be more complete by noting what the purge call itself returns or explicitly warning that the operation is irreversible, but the essential behavior is clear enough for correct invocation.

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 100%, so the schema already documents all four parameters. The description references older_than_versions but adds no new parameter-level detail such as accepted value ranges, defaults, or edge-case behavior.

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 a specific verb ('Drop') and resource ('stored versions of a document') with a retention condition based on older_than_versions. It is clearly distinct from sibling docs.delete, which removes a whole document, and from docs.get/list/put/status.

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 implies when to use this tool: when you want to prune old versions of a document while keeping a certain number of recent ones. However, it does not explicitly contrast it with docs.delete or describe scenarios where this tool should not be used.

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