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

Annotations already establish the safe-read profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real value by disclosing the returned content: daily-scan pass/fail posture, the last manual scan's compliance percentage, failing policies/records, and a company rollup — all useful context given there is no output schema.

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 dense sentence that front-loads the resource and scope before enumerating returned data. It is information-rich without padding, though the parenthetical "(Cloud Compliance)" and the nested enumeration of scan types make it slightly heavy.

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, the description carries the return-value burden and does so well, spelling out both the per-account data and the company rollup. Combined with annotations covering the safety profile and a fully documented single parameter, an agent has everything needed to call it correctly.

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?

There is a single optional parameter and schema description coverage is 100%, with the schema already stating that account_id limits results to one account and that all company accounts are returned when omitted. The description adds no parameter detail, so the baseline 3 applies — the schema does the heavy lifting.

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 names a specific resource (cloud security & compliance posture) and scopes it precisely: per connected cloud account, CIS/NIST cloud-policy scans, daily-scan checks passed/failed, last manual scan compliance %, and a company rollup. It is clearly a read of cloud-specific compliance posture, which separates it from generic siblings like compliance_status and get_framework_coverage, though it never names those siblings explicitly.

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?

Usage is implied rather than stated — an agent can infer this is the tool for cloud-account compliance posture, but there is no explicit when-to-use/when-not guidance and no routing to compliance_scan, compliance_status, or get_framework_coverage, which are the obvious overlapping siblings in this toolset.

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