get_s3_overview

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully states that object contents are never included, and the 'Returns' phrasing implies a read operation. However, it does not mention potential side effects, data freshness, authentication requirements, or operational caveats—though the parameter schema covers caching behavior, the tool description itself lacks full transparency.

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?

Three sentences with no wasted words. The main purpose is front-loaded, followed by explicit usage guidance and a clear exclusion. The structure is efficient and scannable.

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 simple overview tool with one optional parameter and no output schema, the description covers the key return contents and usage boundaries. It lacks a detailed return structure but mentions sufficient fields (versioning, encryption, public access, security findings) to set expectations. The parameter schema compensates for freshness explanations, making it fairly 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?

Schema description coverage is 100%, so the single parameter maxAgeSeconds is fully documented in the schema, including its advisory nature and refresh behavior. The tool description does not add parameter-specific meaning, but the baseline of 3 applies when the schema handles 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 opens with a specific verb and resource: 'Returns all S3 buckets with versioning status, encryption, public access configuration, and security findings.' This clearly defines the tool's scope and differentiates it from siblings by explicitly naming get_infra_overview as the alternative for infrastructure counts.

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?

Explicit when-to-use scenarios are given: checking existing buckets, reviewing security posture, and confirming bucket names before writing handlers. It also states a clear when-not-to-use case ('Do NOT call when you only need a quick infrastructure count') and names the alternative tool, providing strong guidance.

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