ExportOrders

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

Without annotations, the description must disclose behavioral traits. It only states 'request a new ... report exportation to be generated', implying it is a write operation. It does not mention whether the generation is asynchronous, how to check status, or what the response looks like.

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, very concise. However, conciseness should not sacrifice informativeness; a bit more detail could be added without significant bloat.

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's complexity (one nested parameter, no output schema, many siblings), the description is incomplete. It lacks information about return values, processing time, or related tools like 'GetOrderExportations'. The agent would likely need external knowledge to use this tool correctly.

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 sole parameter 'body' is described as 'Request body' in the schema, which is vague. The tool description does not add any meaning beyond this, failing to specify required fields or structure. Despite 100% schema coverage, the description adds no value.

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's action: requesting a new order report export to be generated. It distinguishes from sibling tools like 'GetOrderExportations' (which lists existing exports) by implying creation rather than retrieval. However, it lacks specifics on the export format or content.

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 'GetOrderExportations' is for retrieving previously generated exports, nor does it indicate prerequisites or typical scenarios.

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