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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known. The description adds real substance beyond them: unpaid shares are excluded and the paid remainder becomes a single shop order, which tells the agent what the destructive action actually does. It still omits what happens to partially paid participants and what the response contains.

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 compact sentences with zero filler; the actor and scope come first and the outcome second. Every clause carries 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?

For a three-parameter destructive mutation with no output schema and thin schema coverage, the description covers the action and its main effect but not the return value, error conditions, or what happens to partially paid shares. It is adequate but leaves meaningful gaps an agent would want filled.

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 only 33% — only shop_url is documented in the schema, while code and organiser_key are bare. 'As its organiser' hints that organiser_key is an authorisation credential, but the description never explains the code's format or that shop_url routes the call to a specific shop instance.

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 gives a specific verb ('close') plus resource ('a group order') and scopes it to early closure. It is clearly distinguishable from siblings like group_order_status, start_group_order, and join_group_order, though it never names an alternative 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?

'Close a group order early, as its organiser' implies the precondition (you are the organiser) and timing (before the natural deadline), which is useful. However, it gives no guidance on when to prefer group_order_status first, or what to do if the order is already closed, so usage is only implied.

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