Список S3-хранилищ

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

The description states the tool 'returns' buckets, implying a read-only operation, but the annotation readOnlyHint is false. This is a direct contradiction, making the behavioral disclosure unreliable. No additional behavioral context (e.g., authentication, rate limits) is provided.

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 two sentences, front-loaded with the core purpose, and includes a practical usage tip. Every sentence contributes value with no redundancy.

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?

The tool is simple (no params, no output schema), and the description lists the returned fields and usage context, which is relatively complete. However, the contradiction between the read-only description and readOnlyHint=false undermines completeness, leaving ambiguity about whether side effects exist.

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 tool has zero parameters, and the schema coverage is 100% (an empty properties object). The description does not need to explain parameters, and the baseline for 0 params is 4. The description actually adds value by listing the returned fields, but that is not parameter semantics.

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's purpose: to return all S3 buckets of the account with specific fields. It uses a specific verb ('returns'), resource ('S3 buckets'), and scope ('account'), which distinguishes it from sibling tools like list_project_buckets or list_all_project_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 explicitly says to use this tool before any storage operation to get the bucket ID, providing clear context for when to use it. However, it does not mention alternatives or when not to use it, so it falls short of a 5.

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