Api incidents qualifications breakdown retrieve

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description contributes nothing beyond that and instead suggests a CSV/XLSX export payload, which conflicts with a 'breakdown_retrieve' endpoint. No annotation contradiction is claimed since the format claim is not covered by 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?

It is a single short sentence with no filler, but brevity here comes from under-specification rather than economy. The sentence is a non sequitur relative to the tool name, so nothing useful is front-loaded.

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 domain-specific analytics endpoint with no output schema, the description should at minimum say what the qualifications breakdown contains and at what granularity. It says nothing about the returned data, leaving an agent unable to judge relevance.

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 input schema has zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description neither harms nor helps here.

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 describes an internal implementation artifact ("Generic export mixin") rather than the endpoint's function. It never mentions incidents, qualifications, or a breakdown, and the sibling list already contains dedicated export_csv/export_xlsx endpoints, so the text actively misdirects an agent about what this tool returns.

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?

There is no indication of when to call this versus the many sibling breakdown/retrieve endpoints (e.g. incidents_severity_breakdown_retrieve, incidents_detection_breakdown_retrieve). The one sentence supplies no selection criteria and implies an export workflow that this tool does not serve.

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