report_export_by_order

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

No annotations exist, and the description does not disclose behavioral traits such as read-only nature, side effects, authorization needs, or rate limits. For a report tool, it likely does not modify data, but this is not stated.

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 vague sentence. While concise, it sacrifices clarity and does not front-load key information. The structure does not help an agent quickly understand tool applicability.

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 lack of annotations, low schema coverage, and presence of many sibling report tools, the description is too incomplete. It does not explain the output format, pagination, filtering behavior, or how it differs from similar reports.

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 only 29% (2 of 7 parameters have descriptions). The tool description adds no additional meaning beyond the schema. Parameters like start_date, end_date, warehouse_id, limit, and page remain unexplained.

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 'Warehouse export report grouped by order' indicates a report on warehouse exports grouped by orders, but does not clarify whether it generates a report or exports data, nor what the report contains. It vaguely distinguishes from siblings like report_export_by_sku, but lacks specificity.

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 on when to use this tool versus other report tools (e.g., report_export_by_sku, report_inventories). No mention of prerequisites, limitations, or exclusion criteria. The description provides no usage context.

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