pbs_s3_client_list

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

No annotations provided, so description carries full burden. Declares READ-ONLY, describes response fields (access-key unredacted, secret-key never returned), and mentions configuration requirement. Good disclosure for a list tool.

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?

Two sentences, front-loaded with purpose, no filler. Every sentence adds value: purpose, response details, prerequisite. Highly concise.

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?

With output schema present, no need to detail return values. Covers purpose, read-only nature, response characteristics, and prerequisite. Complete for a list 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 coverage is 100% for the single 'proximo_target' parameter, with a clear description. Description adds little beyond the schema, only referencing dependency on PROXIMO_PBS_* config, which is an environment concern. Baseline 3 is appropriate.

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?

Description starts with 'READ-ONLY: list all PBS S3 client configurations,' clearly stating the verb and resource. It distinguishes from siblings like create/update/delete/get by specifying 'list all'. Response details ('without secret') further clarify scope.

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?

Explicitly marked READ-ONLY, indicating safe usage for listing without modifications. Mentions prerequisite 'Needs PROXIMO_PBS_* config.' Does not explicitly state when not to use or name alternatives, but context implies use for full list vs. specific get.

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