export_inventory

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

Annotations already declare readOnlyHint=true. The description adds meaningful context: full export, CSV format, reimport compatibility, and API key requirement. No contradictions, and the behavior is well-disclosed beyond annotations.

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 consists of two concise sentences. The first sentence defines the action and output, the second adds compatibility and authentication. No unnecessary words. Ideal structure.

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, no output schema, but with annotations present, the description covers the essential: CSV columns, compatibility, auth. It lacks explicit mention of how the CSV is returned (e.g., response body), but is adequate for an agent to understand the tool.

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 tool has no parameters, so baseline score is 4. The description appropriately does not waste space on parameters, as none exist.

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 verb 'Export', the resource 'authenticated user's full card inventory', and the output format 'CSV' with explicit columns. It distinguishes from siblings like 'list_inventory' (which likely returns JSON) and 'import_inventory_cards' (import vs export).

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 full inventory export in CSV format, and mentions compatibility with 'import_inventory_cards' and API key requirement. It does not explicitly state when not to use it versus alternatives like 'list_inventory', but the context of 'full' and CSV is clear.

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