Api incidents object retrieve

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

No annotations are contradicted directly, but with readOnly/idempotent hints already given, the description's job is to add context and instead supplies an unrelated statement about CSV/XLSX export mixins. An agent learns nothing about whether the lookup is by primary key, what happens on a missing id, or what object shape is returned.

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 short, but brevity only counts when the content is correct; here the one sentence is front-loaded with irrelevant implementation detail ('Generic export mixin') and conveys zero actionable 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?

A single-object retrieve with one required, undocumented parameter and no output schema needs the description to explain identity semantics and result shape. Nothing in the description addresses that, so the definition is unusable as written.

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 coverage is 0% and the single required parameter `id` is completely unmentioned in the description. There is no note on whether it is an integer PK, a UUID, or a ref string, which is exactly the gap the description should fill.

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 export helper, not retrieving a single incident object by id. It neither states the verb 'retrieve' nor the resource 'incident', so an agent cannot tell what the tool actually 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 guidance on when to use this tool versus siblings such as api_incidents_list, api_incidents_retrieve, or api_incidents_object_retrieve. The only sentence present points toward export behavior, which is a different set of tools (api_incidents_export_csv_retrieve / export_xlsx_retrieve) and would actively misroute the agent.

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