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

'Read only' duplicates readOnlyHint, but the description goes beyond annotations by disclosing the authentication requirement and the concrete behavior on failure ('the connection asks the customer to sign in on printdash.io'), which is exactly what an agent needs to handle an unauthenticated call. It also enumerates the returned content, though the output schema already covers that.

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 resource and scope, then the safety profile, then the auth prerequisite — a sensible ordering with little waste. The sentence 'Read only.' contributes nothing beyond readOnlyHint and could be dropped, which keeps it from a 5.

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?

The tool is simple (one optional param, output schema present), so the description need not explain return values or pagination. It covers the one non-obvious complexity — the sign-in requirement — and leaves the rest to structured fields, with only the sibling distinction 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?

With 100% schema coverage and a single parameter, the schema already documents 'limit' including the default of 10 and the 'newest first' ordering. The description's phrase 'most recent orders' corroborates the ordering but adds no new syntax, bounds or defaults beyond what the schema states.

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 concrete verb+resource (list recent orders) and scopes it to 'the current buying context', which is meaningful information an agent can't get from the name alone. It stops short of differentiating from the nearest sibling, get_order, so an agent must infer that this is the plural/list counterpart of a single-order fetch.

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?

Usage is implied rather than stated: 'the most recent orders in the current buying context' hints at a browsing/summary use case, but there is no explicit when-to-use or when-not-to-use guidance. No alternative is named, despite siblings like get_order, list_pending_approvals and list_quotes overlapping in scope.

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