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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered. The description adds real behavioral context beyond that: an in-use collection is refused by default and force=true overrides it, and CASCADE silently removes all assignments. It does not describe auth requirements or a return payload, but the key destructive consequence is disclosed.

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 sentences, zero filler, and the core action leads. The force condition and the CASCADE consequence are packed into the follow-up without redundancy.

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 no output schema, the description carries the return-value burden, but for a delete action the outcome (removal plus cascade of assignments) is the essential information and it is present. Annotations cover the safety profile, making this largely complete for the agent's decision.

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 100%, so baseline is 3. The description goes further by explaining the 'why' behind force=true (in-use by agents/prompts/channels) rather than merely restating the schema's 'OMIT for the safe default', adding meaningful semantic weight.

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 (Delete) and resource (knowledge collection) in the opening sentence. An agent can immediately distinguish it from sibling management tools like collections_remove_file, collections_remove_website, or collections_unassign_agent.

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?

Explicitly tells the agent when to pass force=true (collection assigned to agents, prompts, or channels), which is the key conditional for this action. It stops short of naming alternatives, but no sibling offers an equivalent collection-deletion path, so the guidance is contextually clear.

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