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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description adds real context beyond them: access is restricted to the owner via owner_key, and the response exposes personal and payment data (names, phone numbers, payments), which is material for handling and privacy. It does not cover pagination or return shape.

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 front-loaded sentence that names the returned data first and the prerequisites last, with no wasted clauses. The parenthetical field list is dense but still earns its place.

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 read-only lookup with no output schema and zero schema descriptions, it covers the data exposed and the authorization requirement, which is the key gap. It remains silent on result structure, whether all registrations are returned, and pagination or size limits, so an agent knows the gist but not the full contract.

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 0%, so the description must compensate. It helpfully states that both parameters are returned by create_group_order, giving provenance, but it does not explain the role or sensitivity of owner_key as an access credential beyond the ownership hint, nor any format expectations.

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 clearly states the resource — the registrations of a group order (sizes, first names, phone numbers, payments) — and scopes it to the responsible owner. It does not use an explicit verb and only implicitly distinguishes itself from the sibling get_order_status, which handles individual orders.

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?

It implies usage after create_group_order by pointing to where group_id and owner_key come from, and indicates the caller must be the order's manager. It never states when not to use it or how it relates to get_order_status, leaving the when-to-use vs alternatives to inference.

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