get_order_confirmation

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which the description correctly aligns with ('Returns data'). The description adds no further behavioral details (e.g., about optional 'with' parameter behavior, error cases, or rate limits), so it meets the baseline but doesn't exceed.

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 sentence, concise and to the point. It could be more informative but is not overly verbose. However, it lacks structure such as separating purpose from details.

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?

Given no output schema, the description does not explain the return format (e.g., fields included, structure). For a simple get tool with well-known domain, this might be acceptable, but for completeness, it should mention that it returns full order confirmation data. Sibling tools like get_delivery_note have similar brevity, so it's adequate but not exceptional.

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%, so the schema already documents both parameters. The description does not add any extra context beyond the schema, such as explaining how the 'with' parameter works or providing examples. Thus, it meets the baseline of 3.

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 clearly states 'Returns data of specified order confirmation', identifying it as a retrieval operation for a single entity. It distinguishes from sibling tools like list_order_confirmations (listing) and create/update/delete tools. However, it doesn't specify that the order confirmation is identified by ID, which is a minor gap.

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?

No guidance is provided on when to use this tool versus alternatives like get_order_confirmation_preview or list_order_confirmations. The description lacks context on prerequisites, such as needing an existing order confirmation ID, or when to prefer this over other retrieval methods.

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