Api risk matrices object retrieve

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

Annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, but the description says the endpoint allows risk matrices to be "edited" – a write capability that contradicts the read-only annotation. Nothing is added about what the lookup returns, error behavior for unknown ids, or object scoping.

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 wasted clauses, so nothing needs trimming. However, brevity here comes from under-specification rather than density – the one sentence carries almost no actionable content.

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 an object-retrieval tool with one undocumented required parameter and no output schema, the description should at minimum pin down what the id refers to and that a single record is returned. Neither appears, so an agent must guess from the tool name alone.

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?

A single required "id" parameter with 0% schema description coverage, so the description is the only place meaning could be added – yet it says nothing about what the id identifies (UUID? integer? slug?) or which namespace it resolves in. The description contributes no semantic value beyond the schema's key name.

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 names the resource ("risk matrices") but pairs it with the ambiguous verb phrase "viewed or edited", which describes two opposing operations rather than what this specific endpoint does. It never states that this retrieves a single risk matrix by id, so it cannot be distinguished from the sibling risk_matrices_list, risk_matrices_retrieve, or risk_matrices_update tools.

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 when-to-use guidance, no prerequisites, no mention of alternatives despite numerous sibling endpoints on the same resource. The only signal an agent could extract ("viewed or edited") is actively misleading about which sibling to pick.

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