download_inventory_export

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

With no annotations, the description must disclose behavior. It indicates a file download but does not explain error conditions (e.g., invalid ID, incomplete export), data format specifics, or response characteristics. The behavioral transparency is minimal.

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, which is concise but insufficiently informative. It earns its place but fails to add value beyond the tool name. Length is appropriate only if the content were richer.

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 simplicity (1 param, no output schema, no annotations), the description should cover key aspects like the format (CSV) and the nature of the ID. It partially does so but omits crucial details such as expected output type and error handling, leaving the agent underinformed.

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 'id' is not described beyond its type and requirement. Given 0% schema description coverage, the description should explain that 'id' refers to the inventory export's identifier. The tool name offers some implicit meaning, but explicit documentation is absent.

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 ('Download'), the resource ('inventory export'), and the format ('CSV'). It is specific and not a tautology. However, it does not explicitly differentiate from sibling tools like 'get_inventory_export' or 'get_inventory_exports', missing an opportunity to clarify the distinction.

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 or prerequisites (e.g., the export must exist and be ready for download). The description is silent on context, leaving the agent to infer usage.

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