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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely non-obvious behavioral context beyond that: the blast radius is limited to the collection set and the files survive in the library. It does not state whether the deletion is reversible or what happens to nested/referenced items beyond files.

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?

Two short sentences with zero waste; the destructive scope clarification is front-loaded immediately after the action, which is exactly where an agent needs 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?

For a single-parameter destructive tool with annotations covering the safety profile and no output schema, the description covers the key risk (files are preserved). Remaining gaps are minor: irreversibility, preconditions, and how to identify a valid collection ID.

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% for the single required collectionId, and the description says nothing about it — no ID format, no source, no way to obtain a valid value. The verb's object implies the parameter's meaning but adds no information an agent could not guess from the schema.

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 and resource ("Delete a collection") and immediately scopes the effect: only the set is removed, its files remain. That distinguishes it from the many delete_* siblings that destroy underlying assets, though no sibling is named explicitly.

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 second sentence implies the use case (removing an organizational container while keeping the content), but there is no explicit when-to-use/when-not, no prerequisite such as whether the collection must be empty, and no named alternative for deleting the files themselves.

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