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

Annotations already state readOnlyHint=true, and the description reinforces 'Read-only' consistently. Beyond that it discloses non-obvious behavior: an uninstalled-Trivy cluster returns an empty items list rather than an error, access_posture null means the day recorded none (explicitly 'not a clean posture'), and vulnerability_snapshot_recorded false means no scan rather than zero findings. These are genuine interpretation constraints the annotations do not carry.

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?

The purpose is front-loaded, but the body is a dense block of heavily semicolon-and-parenthesis-laden sentences that are hard to parse on first read. Most content is substantive (return-payload field meanings), but the packing reduces scannability.

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?

There is no output schema, so the description carries the burden of explaining the return payload, and it does so thoroughly: items fields (findings by severity, fixable critical/high, workloads/namespaces, risk score, disposition split), access_posture semantics, access_posture_history, and the no-snapshot empty-list case. An agent has what it needs to call and interpret the result 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?

Schema description coverage is 100% and both parameters (days with clamping/default, cluster_id optionality) are fully documented in the schema. The description adds no parameter-level detail beyond what the schema already provides, 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?

States a specific verb and resource with scope: 'daily security posture trend of one cluster from its stored snapshots, oldest first.' An agent can distinguish a historical/temporal series from a current-state tool like get_cluster_security_report_schedule or list_security_cluster_posture. It does not explicitly name any sibling as the contrasting alternative, so it stops short of a 5.

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 by the framing (trend over days, oldest first) but there is no explicit when-to-use / when-not-to-use statement and no routing to alternatives for current posture. It does give valuable operational guidance for edge cases (empty items list when no snapshots exist), which lifts it above pure absence of guidance.

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