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

Annotations already declare destructiveHint=true, but the description adds substantial value beyond them: no undo, stock removal without relocation, tax-rate and product-visibility loss, preserved entities (orders, sessions, reports, stations), and a hard precondition (WooCommerce default outlet refusal). This is exactly the cascade detail an agent needs for an irreversible mutation.

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?

Front-loaded with the one-line purpose, then dense but non-redundant safety detail. The multi-clause sentences are heavy, yet nearly every clause covers a distinct consequence or precondition, so little could be cut without losing critical information.

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?

Single-parameter destructive tool with no output schema; the description covers the safety profile, cascade effects, preserved data, and blocking preconditions. Nothing an agent needs to call this correctly is missing.

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% and the schema already states "Outlet id from get_outlets — not a name." The description repeats the get_outlets sourcing but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ("Close a point of sale permanently") and immediately distinguishes itself from related siblings like hub_update_outlet and hub_delete_station by specifying what is and isn't removed. An agent can identify the operation without opening the schema.

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?

Explicit about when and how to use it: confirm with the merchant first, transfer stock out before deleting if it should be kept, deal with stations separately, and change the WooCommerce default before attempting deletion. Prerequisites and the refusal condition are both named.

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