export_data

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds important behavioral context: the output is CSV, ids narrows to specific row ids rather than exporting everything, and the invoices category cannot be returned as text because it is a zip archive. That is meaningful, non-contradictory detail beyond the structured fields.

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 compact and well ordered: first the main action, then the category requirement, then the optional ids parameter, then a short caveat about invoices. Every sentence serves a distinct purpose and there is no filler.

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?

With only two parameters and an output schema present, the description covers all needed call decisions: required category values, optional ids behavior, and the one category that should not be handled by this tool. An agent has enough information to invoke it 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?

Schema description coverage is 0%, so the description must carry the parameter meaning, and it does. It gives exact allowed category values and explains when ids is valid and what it does, which is far more than the empty schema properties provide.

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 starts with a specific action and resource: 'Export a copy of this account's own data as CSV' and immediately constrains it to 'one category at a time'. It then enumerates the categories, making it easy to distinguish from sibling list/get/create tools, which do not 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?

It clearly says when to use the tool: when a category-scoped CSV export of account data is needed. It also gives a when-not by explaining that the 'invoices' category is a zip archive on the real dashboard and should be downloaded from the dashboard's Export Data page instead, an explicit exclusion.

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