inventory_export

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

The description uses 'request an export' which hints at an asynchronous operation, but it doesn't disclose whether it's destructive, how long it takes, or what the response contains (e.g., export ID). Since no annotations are present, the description carries the full burden but falls short.

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 with no redundant information. It is front-loaded with the action and result.

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 no parameters and a simple concept, the description is mostly complete but lacks mention of the asynchronous workflow and how to retrieve the export (via 'download_inventory_export'). The lack of output schema makes this gap more significant.

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?

There are no parameters, so baseline is 4. The description adds meaning by specifying the output format (CSV), which is not in the schema. No further elaboration needed.

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 action ('request an export') and the resource ('your inventory') and format ('CSV'). It distinguishes from sibling tools like 'download_inventory_export' by implying a request/initiation step. However, it could be more specific about what the export includes.

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 usage for starting an export, but it doesn't explicitly say when to use this vs. 'download_inventory_export' or 'get_inventory_export'. No guidance on prerequisites or alternatives is provided.

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