pbs_s3_list_buckets

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

With no annotations provided, the description fully discloses key behaviors: read-only nature, live outbound call, adversarial content (returned bucket names are external), and config requirements. This is comprehensive and honest, leaving no hidden surprises.

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 (under 100 words), front-loaded with the purpose, and every sentence adds necessary information. No fluff or repetition.

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?

Given the tool's low complexity and the presence of an output schema, the description covers key aspects: purpose, hazards (adversarial), prerequisites (config). It does not mention rate limits or error conditions, but this is acceptable for a simple list operation.

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 description adds value beyond the schema by explaining that s3_id is an operator-configured client config and that 'proximo_target' selects a target. Schema coverage is 100%, so the baseline is 3; the description enriches parameter context without being redundant.

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 starts with 'READ-ONLY: list buckets accessible by the given S3 client configuration', which clearly states the verb (list), resource (buckets), and scope (accessible by given S3 client). It distinguishes itself from sibling tools that manage S3 clients (pbs_s3_client_*) rather than listing buckets.

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 clear context for usage: it is read-only, makes a live call, and requires PROXIMO_PBS_* config. It includes an adversarial warning that guides cautious use. However, it does not explicitly state when not to use this tool or name alternative tools, though no direct alternative exists.

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