Aws Snapshots

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuine value by saying the tool emits findings (retention gaps, failed snapshots, groups without automatic backups), which tells the agent this is diagnostic output rather than a raw list. It says nothing about scope defaults, pagination, or what happens when region is omitted.

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 names the operation first and then the payload. Nothing is redundant, though the comma-list of findings is dense enough to be slightly harder to parse than it needs to be.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. Still missing is any guidance on the scoping parameters (cluster vs replication group), the region default, and how the findings relate to the stale_hours threshold — gaps that matter for a five-parameter audit tool.

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 only 60% and the description contributes no parameter meaning at all. Two parameters (cache_cluster_id, replication_group_id) are undocumented in the schema and completely unaddressed in the description, and the stale_hours threshold interaction is left to the schema.

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 the underlying operation (DescribeSnapshots) and enumerates the reported dimensions (age, size, status, automatic vs manual) plus derived findings. That is a specific verb+resource. It does not, however, distinguish this from sibling snapshot tools such as aws_serverless_snapshots or aws_snapshot_restore_readiness.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The mention of 'findings for retention gaps' implies an audit use case, but an agent must infer that this is the general snapshot audit tool rather than, say, the restore-readiness check.

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