Api incidents export csv retrieve

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

Annotations already supply readOnlyHint, idempotentHint, openWorldHint and destructiveHint, so the safety profile is covered. The description adds nothing beyond that and does not explain what the caller receives (file bytes vs. a URL), whether filters apply, or any permission requirements.

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?

A single short sentence, so it is not bloated, but it is front-loaded with implementation jargon ("mixin") instead of the user-facing action. The size is fine; the content choice is not.

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?

There is no output schema, so the description is the only place an agent could learn the response shape (CSV content, headers, pagination or scope of exported rows). It provides none of that for a download-style endpoint.

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 takes zero parameters, so the baseline is 4. No parameter semantics are needed and none are missing.

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?

"Generic export mixin for CSV/XLSX exports" describes an internal code construct rather than the tool's purpose. It never states that it exports incidents, nor that this endpoint returns CSV specifically (XLSX has a separate sibling). The resource is only identifiable from the tool name.

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 indication of when to use this versus ciso_assistant_api_incidents_export_xlsx_retrieve, incidents_list, or the other export endpoints. The mention of both CSV and XLSX actively blurs the distinction between the two sibling tools.

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