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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description earns credit by disclosing the dual-mode contract and what a no-vendor call returns (vendors plus per-vendor exam counts), which is behavioral information not present in any structured field.

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?

Two sentences, no filler, with the more common no-argument case stated first and the parameterized case second. Every clause carries information an agent needs.

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?

An output schema exists, so return-shape explanation is not required, and the description covers both invocation modes plus the parameter's accepted forms. The remaining gap is failure/edge behavior — whether an unknown vendor errors or yields an empty list — which matters for a lookup tool.

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%, so the description carries the full burden for the single `vendor` parameter, and it does so well: it is optional, accepts either a human-readable name or a short vendor code, and gives four example values. It does not say what happens on an unmatched or abbreviated vendor string.

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 and, more usefully, the two distinct behaviors the tool has depending on whether `vendor` is supplied: vendor+count enumeration versus per-vendor exam listing. It never names `search_exams` as the alternative, so an agent must infer when to prefer the search sibling over this listing.

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?

Explicitly frames the two call modes ('Without a vendor...' / 'With a vendor...') and gives concrete accepted value shapes — a display name like "Microsoft Azure" or a code like "aws", "iapp", "isc2". That is real procedural guidance, but there is no statement of when to reach for `search_exams` instead.

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