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

Annotations only declare readOnlyHint=true; the description adds substantial behavioral context beyond that — the output is bounded, a focused request returns only that exact control and reports whether it matched, and benchmark_id is required when source is benchmark. It stops short of auth/rate-limit or pagination behavior, so 4 rather than 5.

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?

Purpose and scope are front-loaded in the first sentence, and the routing guidance comes last. Five sentences is slightly dense, but each carries distinct information (returns, focus semantics, constraint, routing) with no filler.

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?

No output schema exists, so the description carries the return-value burden and does so explicitly — benchmark identities, pass/fail totals, failed controls with severity/remediation/affected counts, passed controls, and config-audit severity/namespace/top-check rollups. Combined with the focus behavior, an agent has enough to call and interpret it.

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 100%, so baseline is 3; the description adds meaning by explaining the focus object's intent ('For one selected finding, pass a focus object with check_id and source') and the conditional benchmark_id requirement, which clarifies how the nested params interact.

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 with scope: 'Get the Trivy Operator compliance posture for the current cluster.' It also explicitly names the boundary against a sibling ('use get_security_reports for image vulnerabilities and CVEs'), so an agent can separate it from the vulnerability-reporting tools without opening a schema.

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?

Gives explicit when-to-use ('CIS, NSA/CISA and other compliance-benchmark questions'), an explicit alternative ('get_security_reports for image vulnerabilities and CVEs'), and a when-not constraint ('Do not broaden a focused remediation request to unrelated controls').

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