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

Annotations already advertise destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds the meaningful nuance of 'soft-delete', which signals the data is likely recoverable rather than permanently destroyed—information the annotations do not capture. It stops short of explaining recovery or whether already-deleted items error.

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?

A single tight sentence with the key qualifier ('Soft-delete') front-loaded. The odd 'seliee_collection' token is sloppy but doesn't waste space.

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 simple two-param delete with annotations covering the safety profile, most essentials are present. Missing the crucial constraint that one of the two nullable identifiers must be given, plus precedence behavior, leaves a real gap 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 coverage is 0%, so the description must carry parameter meaning; it names collection_id and collection_uuid and frames them as an either/or selector. However, it doesn't state that at least one must be supplied (both are nullable/optional) or which takes precedence when both are provided.

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?

States a specific verb+resource ('Soft-delete a collection') and identifies the two identifiers used to target it. Clear what it does, though it doesn't differentiate from other delete_* siblings beyond the resource name.

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 on when to use this versus edit_collection, or what happens after a soft-delete (restore path). An agent is left to infer the appropriate conditions from the tool name alone.

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