Connect AWS

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description goes beyond by explaining the propose-then-confirm flow, that it never creates/modifies/deletes anything in the AWS account, and that credentials stay local. This adds significant behavioral context beyond the annotations, covering safety and data handling.

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 and well-structured: it starts with a clear purpose, then explains the propose-then-confirm flow, includes usage examples, and is front-loaded with the most important info. 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's complexity (one optional parameter, no output schema, but with safety considerations), the description is quite complete. It explains what happens, what it doesn't do, and how to use it. Minor gap: it doesn't describe what the output looks like (e.g., a list of accounts or a connection confirmation), but since there's no output schema, this would be helpful. However, the description still provides enough for an agent to use it effectively.

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 schema has one parameter, account_id, with no description in the schema. The tool description explains its use: 'call it again with account_id set to the one to connect,' which adds meaning. However, it doesn't specify the format of account_id (e.g., numeric string), but the schema coverage is 0%, so the description partially compensates but could be more detailed.

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: connecting an AWS account from the MCP client using existing local credentials. It distinguishes itself from siblings like connect_azure and connect_gcp by explicitly naming AWS and detailing its scope (no terminal needed, local-only).

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 explicit usage guidance: call with no arguments first to list available accounts, then call again with account_id set. It also gives example prompts. While it doesn't explicitly mention alternatives, the context of siblings is clear, and the instructions are actionable.

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