scan_s3_bucket_key_opportunities

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It implies a read-only scan by stating 'Finds' and 'Returns', but does not explicitly confirm non-destructive behavior, required permissions, scope (single account vs. all accounts), or any potential costs from API calls. This leaves significant gaps for the AI agent.

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 description is concise: two sentences that state purpose, benefit, and output, followed by two illustrative example queries. Every sentence adds value, and the structure is front-loaded with key information.

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 tool with no parameters, no output schema, and no annotations, the description covers essential purpose and output. However, it lacks operational context such as whether it is read-only, scope of scan (single account or all linked accounts), prerequisites (connected AWS account), and how to interpret results. This is adequate but not fully complete.

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?

The input schema has zero parameters, so the description does not need to add parameter details. It effectively clarifies the implicit scope by specifying the target resource (S3 buckets with KMS encryption without bucket keys). This adds meaningful context beyond the empty 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 clearly states the tool scans S3 buckets using KMS encryption without Bucket Keys enabled, explains the benefit (up to 99% reduction in KMS API calls), and specifies output (affected buckets with CLI fix command). It distinguishes from sibling auditing 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?

The description provides example queries that illustrate when to use this tool, such as 'Find S3 buckets missing bucket keys' and 'How much are we wasting on KMS calls from S3?'. However, it does not explicitly state when not to use it or compare with alternative tools like 'scan_waste_patterns'.

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