connect_s3

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

No annotations are provided, so the description carries the burden. It discloses connection modes, credential requirements, and region auto-detection, but does not mention side effects (e.g., session creation, network requirements) or whether the connection is persistent. Adequate but not comprehensive.

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, using two sentences and bullet points. It is front-loaded with the main purpose and every sentence adds value. No wasted words.

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 has 5 parameters, two modes, and no output schema, the description covers the accepted URL formats, mode conditions, and auto-detection. It is sufficient for an agent to understand how to invoke the tool correctly, though return value behavior is omitted.

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 parameters are well-documented in the schema. The description adds extra meaning by explaining the two modes and how parameters relate (e.g., region auto-detected, credentials required for private), adding value beyond the schema.

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 connects to an AWS S3 bucket and distinguishes two modes (credentials vs public). It is specific about the resource (S3 bucket) and the verb (connect), and it differentiates from sibling tools which are object operations.

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 explains when to use each mode: credentials for private buckets, public mode for public buckets. It provides clear context on prerequisites and auto-detection, but does not explicitly state when not to use the tool or mention alternatives beyond siblings.

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