get_order

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

No annotations are provided, so the description carries the burden of behavior disclosure. The verb 'Get' indicates a read-only retrieval, and 'all available details... including execution information' specifies the return scope, but there is no mention of auth requirements, error behavior, or rate limits. No contradiction with annotations, since none exist.

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 concise sentence that front-loads the verb and resource, with no fluff. It efficiently communicates scope and adds the execution-information detail.

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 is a simple getter with an output schema, so return values are covered elsewhere. However, the description lacks explanation of the required account_seq parameter and doesn't state any conditions like account ownership, making it incomplete for an agent without domain knowledge.

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%, and the description does not explain the parameters. It only mentions 'one order', which helps infer order_id's role, but account_seq is left undocumented. The description adds minimal meaning beyond the parameter names.

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?

Description clearly states 'Get all available details for one order', identifying the verb (Get), resource (order details), and scope (single order). The phrase 'including execution information' adds specificity beyond the name and distinguishes it from the plural sibling get_orders.

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 implies use for a single order by saying 'for one order', but does not explicitly mention alternatives like get_orders or conditions for when to use this tool over others. No when-not-to-use or prerequisite guidance is provided.

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