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

Annotations already declare readOnlyHint=true, so the trailing 'Read-only' is largely redundant. However, since there is no output schema, the enumeration of returned fields (including nested ticket items and their check-in state) is genuine behavioral disclosure that tells the agent what it gets back. Missing is any note on not-found behavior or permission requirements.

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?

One dense sentence: verb and key first, then the field inventory. Nothing is wasted and the identifier constraint is front-loaded.

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 compensates by listing the returned structure, which is what an agent needs to decide whether to call it. Only the failure mode (unknown orderId) is unaddressed.

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?

Single parameter with 100% schema description coverage ('Order id.'). The description says 'by id' but adds no format, source, or derivation detail beyond the schema, 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 and resource with a clear scope qualifier: fetch ONE order by id, followed by the exact payload contents (buyer, state, cost breakdown, time slot, checkout answers, ticket items with check-in state). This implicitly separates it from universe_list_orders, which returns many. It stops short of naming the sibling explicitly, which keeps it from a 5.

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?

The 'by id' phrasing implies the lookup use case, but there is no explicit statement of when to prefer this over universe_list_orders or universe_list_attendees, and no prerequisites or error conditions mentioned. Usage is inferable but not stated.

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