Orders_Retrieveanorder

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

The description only states the action 'Retrieve' without disclosing behavioral traits such as read-only nature, authentication requirements, or side effects. Since no annotations are provided, the description carries full burden but fails to deliver.

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 short but lacks substance. It is front-loaded with the verb but provides no further details, earning a middle score for conciseness without completeness.

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 the tool has 6 optional parameters, no output schema, no annotations, and a confusing relationship with a sibling list tool, the description is severely incomplete. It fails to explain behavior, parameter roles, or differentiation.

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?

Although schema coverage is 100%, the parameter descriptions are tautological (e.g., 'Query parameter: include'). The tool description adds no additional meaning or usage context for the parameters.

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 'Retrieve an order' is essentially a tautology of the tool name 'Orders_Retrieveanorder'. It does not clarify whether this retrieves a single order or lists orders, and fails to distinguish from the sibling 'Orders_Listallorders'.

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 'Orders_Listallorders'. The optional parameters and lack of required order ID create ambiguity about its intended use case.

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