fetchOrder

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

The annotations include readOnlyHint=true, which already informs the agent that this is a safe, read-only operation. The description adds no further behavioral context such as error handling, rate limits, or authentication requirements. With annotations covering the safety profile, a score of 3 is appropriate.

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?

The description is a single concise sentence that is front-loaded with the verb. It is not verbose, but could be improved by adding just a few more words to differentiate from siblings. Given the minimal size, it scores well but not top marks due to missing context.

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 has 4 parameters (including a nested credentials object) and no output schema, yet the description does not explain the return format, what happens if an order is not found, or how to use the credentials parameter. For a tool that retrieves a specific resource, more contextual completeness is expected.

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 75% (only orderId lacks a description). The description does not add any parameter-level information beyond what the schema already provides. In particular, the important orderId parameter remains undocumented anywhere except its type, leaving the agent to guess its format.

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?

The description 'Fetch a specific order by ID' clearly states the action (fetch) and the resource (specific order by ID), effectively distinguishing it from sibling tools like fetchAllOrders, fetchOpenOrders, etc. It is specific and unambiguous.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention that it should be used when a specific order ID is known, nor does it reference sibling tools for listing or comparing orders. An agent would have to infer usage from the tool name and parameters.

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