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

readOnlyHint=true and openWorldHint=false already declare the safe-read, closed-world profile, so the description's main added value is the company-wide, all-framework scope. It adds no detail on aggregation behavior, freshness, or what the rollup contains, leaving the behavioral picture thin beyond what the annotations provide.

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?

A single front-loaded sentence that packs scope, frameworks, and intended use with zero filler. Nothing redundant and nothing to trim.

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 read-only, zero-required-parameter aggregation tool with no output schema, the description conveys what the result represents (company-level posture across all frameworks) and who consumes it. Only minor gaps remain, such as how the optional scan_id/diagram_id filters change the rollup.

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 scan_id and diagram_id are already documented in the schema. The description never references either filter, adding no semantics beyond the baseline for fully covered parameters.

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 (rollup) and resource (company-level compliance posture) and enumerates the frameworks covered, which distinguishes it from the per-framework tools like get_framework_coverage and get_cloud_compliance. It stops short of naming a sibling or explicitly contrasting itself with compliance_scan, which likely initiates the scan this tool summarizes.

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 hints at context via "suitable for CI gates and executive reporting," which implies read-only aggregation use, but it never states when to prefer this over compliance_scan, get_framework_coverage, or get_cloud_compliance. Usage must be inferred rather than read.

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