Api incidents export xlsx retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds no useful behavioral context such as what data is included, whether the export is filtered, how it is delivered, or any permissions implications. It also refers to CSV/XLSX generically even though this endpoint is specifically XLSX.

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?

It is a single short sentence with no filler, but it is under-specified and not front-loaded with the actual tool-specific purpose. Brevity does not compensate for the missing information.

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?

For a zero-parameter export endpoint, the description should at minimum identify the resource and output format ('Export incidents to XLSX'), and ideally mention that it returns a file download. Instead it only describes an internal mixin, leaving key context to the name and annotations.

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 zero parameters, so the schema is complete and the description does not need to explain parameter usage. Baseline for zero params is 4.

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 says only 'Generic export mixin for CSV/XLSX exports,' which is an implementation-oriented restatement of the export concept rather than a specific statement that this tool exports incidents to XLSX. It does not distinguish this tool from the sibling incidents_export_csv_retrieve or the many other export_xlsx tools.

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 gives no guidance on when to use this XLSX export versus the sibling CSV export or other export endpoints. There are no conditions, prerequisites, or alternative-tool routing.

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