Api risk matrices impact retrieve

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

The description claims the endpoint allows risk matrices to be "viewed or edited", while annotations declare readOnlyHint=true and destructiveHint=false. Claiming an edit capability on a read-only retrieve endpoint is an annotation contradiction; the description also adds nothing about what the impact payload contains.

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?

One short sentence with no padding, so it is structurally fine, but it is boilerplate that carries no front-loaded information specific to this operation. Brevity here comes from under-specification rather than disciplined writing.

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?

With no output schema, no parameters, and a retrieve endpoint, the description is the only place to say what an "impact" object looks like or how it differs from probability/risk data. It says nothing beyond a generic view/edit claim, leaving the agent without enough to invoke it confidently.

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 and the schema coverage is 100%, so there is nothing for the description to clarify. Baseline 4 applies for a parameterless call.

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 sentence is generic DRF boilerplate that restates the resource ("risk matrices") without naming the specific operation this endpoint performs. The tool name says "impact_retrieve", yet the description never mentions impact levels or that this returns a taxonomy/choice list, so it cannot be distinguished from siblings like risk_matrices_retrieve, risk_matrices_probability_retrieve, or risk_matrices_colors_retrieve.

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 when-to-use guidance and no mention of alternatives, despite hundreds of sibling tools including several near-identical risk-matrix retrievals (probability, colors, risk, ids). The agent must guess from the tool name alone which one yields impact values.

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