Api incidents pdf retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing about how the export behaves (page layout, locale, whether the PDF is generated on the fly or cached) and instead makes a format claim that conflicts with the tool's own name.

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 padding, so structurally fine. However, brevity here comes at the cost of being wrong, so it earns no credit beyond being compact.

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 one-parameter PDF export with no output schema, the description should at minimum confirm it returns a PDF for the given incident. Instead the only content is a generic mixin note, leaving the return type, the meaning of 'id', and the relationship to the CSV/XLSX export siblings all unresolved.

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?

There is one required parameter ('id') with 0% schema description coverage, and the description says nothing about it. The agent must infer that 'id' is the incident identifier being exported, which is plausible but nowhere confirmed; this is a case where the description was needed to compensate for the schema and did not.

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 'Generic export mixin for CSV/XLSX exports', which describes an internal implementation base class rather than what this tool does. The tool name and title indicate a PDF retrieval for incidents, so the description actively points the agent at the wrong format and never names the resource (incidents) at all.

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 tool versus the many siblings such as ciso_assistant_api_incidents_export_csv_retrieve, incidents_export_xlsx_retrieve, or incidents_md_retrieve. The only stated format (CSV/XLSX) is the opposite of what a PDF endpoint would be used for, so the guidance is misleading rather than merely absent.

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