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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: the conditional pay_url only appears 'when the business takes card payment', and it discloses a privacy boundary (never returns buyer address, email or phone) that no annotation conveys.

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?

Three tight sentences: the returned fields come first, the required inputs next, and the privacy constraint last. The enumeration is dense but each element earns its place by telling the agent what it will receive.

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 no output schema, the description correctly carries the burden of describing return values, including the conditional pay_url, and adds an explicit privacy guarantee. It omits failure behavior (not-found or invalid reference) but is otherwise sufficient for a two-parameter read tool whose annotations cover the safety profile.

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%, so the baseline is 3. The description goes slightly beyond the schema by tying 'reference' to its provenance ('the reference the order answer gave') and identifying 'domain' as the business domain, which helps the agent map values from the place_order response into these fields.

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?

Specific verb+resource: returns the outcome of an order created by place_order, and enumerates the concrete payload (status, item, quantity, total, paid flag, pay_url). It explicitly anchors itself to the sibling tool place_order, so an agent can distinguish it from request_quote or list_business_offerings immediately.

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 establishes the precondition for use - 'Takes the business domain and the reference the order answer gave' - which tells the agent this is a post-place_order lookup and where the reference comes from. It stops short of naming when to prefer an alternative (e.g. for a quote rather than an order) or what happens if the order is unknown.

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