Api risk matrices export yaml retrieve

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds meaningful context that the output is 'library-compatible' (i.e., re-importable), but says nothing about delivery mechanism (file download vs inline text), or what happens if the id is a draft or unknown.

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 front-loaded sentence with no filler and no repetition of the title. It is appropriately sized for a simple read endpoint, though it leaves room that could have been spent on the id semantics rather than being maximally terse.

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 one-parameter read tool with rich annotations and no output schema, the description covers what the tool produces at a high level. However, it omits the identifier semantics and the shape of the return (download link vs YAML string), which are the two things an agent would still need to call it correctly.

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 parameter 'id' has 0% schema description coverage, so the description is the only place to clarify whether it is a matrix UUID, a ref_id, or a name. It provides none of that, leaving the caller to guess the identifier type.

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?

States a specific verb and resource plus a format qualifier: 'Export a matrix as a library-compatible YAML file.' An agent immediately knows this produces a YAML serialization, but the description does not differentiate it from near-neighbors such as risk_matrices_retrieve or risk_matrices_import_yaml_create (its inverse).

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 or when-not guidance, and no mention of the complementary import_yaml_create sibling that would make the round-trip intent obvious. The use case is only inferable from the tool name and the phrase 'library-compatible'.

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