Api risk matrices provider retrieve

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

The annotations declare readOnlyHint=true, but the description says risk matrices can be 'viewed or edited,' implying write capability. This directly contradicts the structured safety metadata and gives the agent a misleading behavioral signal.

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 front-loaded sentence with no wasted clauses. However, the sentence is boilerplate and creates ambiguity rather than useful precision.

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 zero parameters and no output schema, the description should at least explain what a 'provider' retrieval returns and how it differs from other risk-matrix endpoints. Instead it gives only a generic view/edit statement that is both ambiguous and inconsistent with the read-only annotation.

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 has zero parameters, so there is no parameter semantics burden on the description. The baseline for a parameterless tool applies, and no incorrect parameter information is present.

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 only says the endpoint allows risk matrices to be 'viewed or edited,' which is generic and does not clarify whether this is a list, single-object retrieval, provider metadata lookup, or mutation. It does not distinguish itself from the many risk-matrices siblings such as list, retrieve, object_retrieve, or update.

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 risk_matrices_list, risk_matrices_retrieve, risk_matrices_object_retrieve, or other risk-matrix operations. The phrase 'viewed or edited' does not route the agent to the right alternative.

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