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

Annotations already declare readOnlyHint=true, so 'Read-only' is confirming, not new. The genuinely valuable addition is the coverage semantics: clusters with SBOM generation switched off are absent rather than shown empty, which prevents a false 'no images' conclusion. That is a non-obvious behavioral trait beyond the annotations, though nothing is said about pagination limits or scan freshness.

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 sentences, front-loaded with what is listed before the usage note and the coverage caveat. Each sentence carries information, though the final coverage sentence is long and slightly overpacked for its point.

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 no output schema and nine optional parameters, the description compensates by summarizing the returned fields and warning about the coverage block's absence semantics. It is complete enough to call correctly, but says nothing about default paging behavior or result ordering, which matter for a 9-parameter list endpoint.

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% across all 9 parameters, so the schema already documents filters, sorting, and paging. The description adds no parameter-level meaning (e.g. whether namespace/cluster_id filters combine or how 'search' tokenizes), so the baseline 3 applies.

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?

Names a specific verb and resource ('List the container images that publish a bill of materials') and enumerates the payload fields (base OS, component count, where they run, attributed findings), so an agent knows exactly what comes back. It also names a downstream sibling, get_security_sbom_image, which anchors it against the other SBOM list tools.

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 states the intended workflow: 'Use it to find an image's identity before calling get_security_sbom_image.' That is clear context, but it does not distinguish this tool from close alternatives such as list_security_sbom_components or list_security_sbom_containers, nor state when this list is the wrong entry point.

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