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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by disclosing the shape of the result (membership, items, payment, closed/collected state), which annotations cannot convey. It says nothing about lookup failures, invalid codes, or permission constraints on viewing other participants' payment status, so it is helpful but not rich.

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?

A single compact clause with zero filler, and the most important payload (who is in the order and whether it has closed) is front-loaded. It is a sentence fragment without a verb, which slightly weakens readability but costs no length.

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 only two parameters and no output schema, the description does well to pre-announce the return content, which is the main complexity here. What is missing is the required `code` semantics and any note on error behavior or the shop_url default. Adequate but with a real gap around the one required input.

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 description coverage is only 50%: shop_url is documented, but the required `code` parameter has no schema description at all, and the description never mentions it. An agent must guess that `code` is a group-order join code with a 4-12 character constraint and no stated format or case sensitivity. With a required, undocumented parameter, the description needed to compensate and does not.

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 enumerates exactly what the tool surfaces about a group order: membership, items ordered, payment state, and whether it has closed and been collected. That is a clear, specific resource with a concrete information payload. It stops short of naming a verb or distinguishing itself from the sibling order_status, which likely reads similarly, so it falls at 4 rather than 5.

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?

There is no when-to-use guidance and no mention of alternatives. The sibling set contains both order_status and get_pickup_pass, and the description does nothing to route an agent between them or to say when a group-order lookup is the right call versus join_group_order or close_group_order. Usage is only inferable from the returned-field list.

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