Api risk matrices destroy

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description describes a view/edit endpoint and says nothing about permanent deletion, required permissions, or what happens to dependent objects (risk assessments, risk scenarios referencing the matrix). This actively misleads about the operation's consequence.

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 it is fine, but the brevity comes at the cost of saying nothing useful about the actual operation.

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 destructive, irreversible endpoint with no output schema and zero annotation-independent context in the description, the definition omits everything an agent needs: that the record is deleted, consequences for referencing objects, and confirmation behavior.

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 single required 'id' parameter has 0% schema description coverage, so the description must supply meaning; it adds nothing about what the id identifies or that it must reference an existing risk matrix. Only the trivial one-parameter shape keeps this above a 1.

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 text is generic Django-REST boilerplate ('allows risk matrices to be viewed or edited') that never says this endpoint deletes a risk matrix, despite the tool name ending in _destroy. An agent reading only the description would conclude it is a read/write endpoint, not a deletion endpoint.

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, no mention of prerequisites (e.g. matrix must not be in use), and no differentiation from the many sibling endpoints such as risk_matrices_retrieve, risk_matrices_update, or risk_matrices_discard_draft_create. The phrase 'viewed or edited' actually points toward the wrong siblings.

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