Check bucket exists

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's '[READ]' tag merely restates that. It adds no non-duplicative behavior: it omits the key trait of a HeadBucket call (success/failure signaling when the bucket is absent) and says nothing about permissions or error responses.

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?

It is a single short line and front-loaded, so it is not verbose. But it is under-specified rather than genuinely concise — the brevity comes from omission of substance, not from economy.

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?

No output schema exists, so the description must explain what a caller gets back from a 'check exists' call, and it does not. For an existence-check tool the success/failure contract is exactly the missing piece, making the definition incomplete despite its simplicity.

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 0% and the single 'bucket' parameter is undocumented in both schema and description. Baseline is softened only because the lone parameter is self-evident from the tool name, but the description contributes no format, naming, or scope detail.

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 concrete operation (S3 HeadBucket) and flags it as a read, and the title supplies 'check bucket exists'. However, the description text itself is a bare identifier plus an SDK reference, so the actual purpose is carried mostly by the title rather than the description, and it never distinguishes itself from the sibling list_buckets or head_object.

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 when-to-use guidance at all. The agent is not told when to prefer head_bucket over list_buckets (which would also reveal existence) or how to interpret the result, and no prerequisite or failure condition is mentioned.

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