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

Annotations already declare readOnly/idempotent/no-destruction, so the safety profile is covered; the description adds genuinely new behavior — a signed-in Printdash account is required and the connection prompts sign-in on printdash.io when missing. It also surfaces conditional capabilities (cancellable? invoice available? reorderable items?) that tell the agent what state checks are possible.

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 core purpose, then auth caveat at the end where it belongs. The long mid-sentence field enumeration is somewhat redundant against the output schema, but it is a single well-formed sentence with no filler.

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?

Output schema exists, so the field list is extra rather than necessary; the key non-schema information an agent needs — the sign-in requirement and what happens without it — is present. Only missing piece is explicit guidance on where this fits relative to cancel_order/reorder workflows.

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 100% and the single `order` param is fully documented there, including that an order id from a link is accepted. The description's "by its order number" adds no syntax or format detail beyond that, so baseline 3 applies.

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 specific verb+resource with scope: "One order by its order number" — immediately distinct from list_orders, which returns many. The enumeration of returned fields confirms this is a single-record fetch, not a search.

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?

"One order by its order number" implies you need a known order number, which implicitly routes agents away from list_orders/search. But it never explicitly says when to use this versus list_orders, or that it should be called before cancel_order/reorder to check eligibility — even though the description mentions cancellability and reorderable items.

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