get_order

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

The annotation readOnlyHint=true already establishes this is a non-mutating read, so the safety profile is covered. The description adds nothing beyond that — no note on not-found/error behavior, identifier format expectations, or scope of the returned record.

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?

A single short sentence with the lookup key front-loaded and zero filler — well sized for the task. It loses a point only because it is terse to the point of under-specification rather than being efficiently informative.

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?

For a trivial one-parameter read tool with a readOnly annotation and no output schema, the description is minimally adequate. It nevertheless omits error behavior and how this differs from list_orders, leaving real gaps at the edges.

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 0%, so the description carries the full burden for the single parameter. 'By id' merely restates the parameter name order_id and gives no format, type, or example, adding essentially no meaning over the schema.

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 ('Look up') and resource ('an order') scoped by identifier, which is unambiguous on its own. However, it offers no differentiation from the closely related siblings list_orders and get_product, so an agent must infer which retrieval tool applies.

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?

There is no guidance on when to use this versus list_orders (fetch many) or the other get_* tools. No prerequisites, no mention of what happens if the id is unknown, and no indication of the intended call context.

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