get_order

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the return includes line items and totals, but does not mention error handling, authentication requirements, rate limits, or side effects (though as a read operation side effects are unlikely). Basic behavior is covered, but deeper context is missing.

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, front-loaded sentence with no unnecessary words. It communicates the main action and key details efficiently.

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 simple get tool with one parameter and an output schema present, the description covers the essential purpose and return content. It does not discuss error cases or alternative tools, but these are less critical for a basic retrieval operation. The description is adequate if not exhaustive.

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?

The input schema provides only the parameter name and type (string), with zero description coverage. The description adds meaning by stating the order is retrieved 'by its id', clarifying the parameter's role. For a single self-explanatory parameter, this is sufficient compensation.

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 the tool retrieves a single order by its ID, including line items and totals. This specific verb-resource combination distinguishes it from sibling tools like list_orders (which likely lists multiple 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 when you need a single order's details, but it does not explicitly mention when to use list_orders instead or any exclusions. Guidance is implied rather than directly stated.

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