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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds value by specifying the human-approval requirement before deletion. It does not describe permanence or cascading effects, but the confirmation context is a meaningful behavioral disclosure beyond the annotations.

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 two short sentences with no filler. The core action is stated first, and the critical safety precondition follows immediately. Every word earns its place.

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?

The description, schema, and annotations together cover the destructive nature and the confirmation requirement, but the role of the uuid parameter is left entirely to inference. The description also does not indicate what happens after deletion, such as whether the deletion is permanent or affects linked content.

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?

The schema only describes the 'confirmed' parameter, and the description's confirmation line mostly restates that. The 'uuid' parameter has no schema description, and the tool description never explains that uuid identifies the collection to delete. With 50% schema coverage, the description fails to compensate for the undocumented uuid 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 clearly states a specific verb ('Delete') and resource ('collection'), which directly distinguishes this tool from siblings like split_update_collection and split_delete_section. There is no ambiguity about what operation this tool performs.

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 instruction 'Confirm with the creator first' provides an explicit precondition for when this tool should be invoked, which is especially important for a destructive operation. It does not explicitly name alternatives or say when not to use it, but it gives clear contextual guidance.

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