Api resilience asset assessments risk matrix retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description contributes nothing beyond that — no note on what is returned, whether a matrix may be absent, or any auth/scope requirement — so it neither adds value nor contradicts the 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 short, but the brevity is under-specification rather than conciseness: a single duplicated identifier carries no front-loaded information an agent can act on.

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 retrieve endpoint with one undocumented parameter and no output schema, the description should at minimum identify the target entity and what the id resolves to. Neither is present, so an agent cannot confidently call this tool or interpret its result.

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 description coverage is 0% and the single required parameter 'id' is undocumented anywhere. The description does not clarify whether id refers to the assessment, the risk matrix, or another entity, so it fails to compensate for the schema gap.

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 is the tool name verbatim ('api_resilience_asset_assessments_risk_matrix_retrieve'), a tautology that adds no verb/resource phrasing beyond the identifier. An agent can only infer from the name that it retrieves a risk matrix tied to a resilience asset assessment, and nothing distinguishes it from siblings like ..._retrieve or ..._quali_impact_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 guidance at all about when to call this versus the sibling ..._resilience_asset_assessments_retrieve or ..._object_retrieve, nor any prerequisites or exclusions. The description is purely a restatement of the name, leaving selection entirely to inference from naming.

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