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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail beyond that: it discloses the side effect of stopping waiting topics and clarifies the partial-destruction boundary ("Collections already written stay"), which tells the agent the operation is not a full purge. It does not say what happens on a second call despite the idempotent hint, nor what happens if the order is already gone.

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 tight sentences with zero filler: the action and identifiers come first, followed by the side effects. Every clause carries information an agent needs.

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 two-parameter destructive mutation with no output schema, the description covers the core action, the identifier options, and the blast radius of the deletion. The remaining gap is the at-least-one-identifier requirement, which matters given both parameters default to null.

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% and both parameters are nullable with no required field, so the description carries real weight. Saying "by `order_id` or `order_uuid`" usefully signals that either identifier alone suffices, which the bare schema does not convey. However, it does not address what happens if both are supplied or if neither is, leaving the mutual-exclusivity contract underspecified.

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 opens with a specific verb and resource ("Delete a collection order") and names the two accepted identifiers, so an agent can distinguish it from delete_collection, delete_articles_order, and edit_collections_order. It stops short of explicitly naming those siblings as alternatives, but the operation is unambiguous.

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?

Usage is implied by the verb and the identifier list, but there is no explicit guidance on when to delete an order versus editing it or deleting the parent collection, and no prerequisites or exclusions are stated. An agent can infer the context but must reason about it.

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