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

With no annotations, the description carries the full disclosure burden. It does useful work by enumerating the return payload (title/identifier, vendor, severity, affected products, vulnerabilities, published date) and framing the tool as a pure fetch. However, it says nothing about behavior when the UUID is not found, whether results are cached or permission-gated, or any rate limits.

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?

Three tight sentences: purpose and return shape first, then fallback resolution, then the alternative tool for adjacent use cases. No filler and correctly front-loaded.

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?

There is no output schema, so the description must convey return values, and it does so field by field. For a single-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning by reinforcing that the identifier must be an advisory UUID specifically and by explaining how to obtain one via listAdvisories. That is real semantic value beyond the schema text.

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 opens with a specific verb and resource – 'Fetch a single Mallory advisory by identifier (an advisory UUID)' – and states that it returns full detail. It is distinguishable at a glance from listAdvisories and queryApi, which are both named.

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?

It gives an explicit routing rule for the main ambiguity: if you only have a name or search terms, call listAdvisories first to resolve the identifier. It also excludes relationship pivots and cross-entity queries, directing those to queryApi.

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