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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: line_offset/line_limit slice locally after a full fetch, the fetch is bounded by the response-size limit, and attachments, addresses and notes are omitted. These are non-obvious traits an agent cannot get from the structured fields.

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 payload, followed by the slicing caveat and exclusions; every clause is informative. The closing 'Does not change the order' largely restates the readOnlyHint annotation, a small redundancy.

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 does the work of describing the return shape (summary + bounded line page) and what is excluded. It leaves open edge cases such as unknown order numbers or behavior when an order exceeds the response-size limit.

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 0%, so the description must carry the load, and it does for the two non-obvious parameters: line_offset/line_limit are explained as post-fetch local slicing rather than server-side paging. order_number itself is left to the schema pattern, which is acceptable since its meaning is self-evident.

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 (Read) and a precise resource (an order summary plus a bounded page of line quantities and prices), which implicitly separates it from the plural list tool rackbeat_orders. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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 only implied: you call it when you have a single order_number. There is no explicit guidance on when to prefer this over rackbeat_orders or what to do when the order is too large, though the local-slicing sentence hints at the trade-off.

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