AWS MCP Server

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

With no annotations provided, the description carries full burden. It discloses what data is returned (master account, feature set, ARN) but omits critical behavioral context: whether this requires AWS Organizations to be enabled, what error occurs if not, that it is read-only (implied by 'Describe' but not explicit), or required IAM permissions.

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?

Single sentence, zero waste. The parenthetical is front-loaded with essential distinguishing information (what 'describe' actually returns). Every word earns its place.

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?

For a simple 2-parameter describe operation, the description is minimally adequate. It compensates for the missing output schema by listing the three key fields returned. However, lacking annotations and behavioral details (auth requirements, preconditions), it meets but does not exceed the minimum viable threshold.

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% with both profile and region well-documented in the schema itself. The description adds no parameter-specific guidance, which is acceptable given the complete schema documentation (baseline 3 per rubric).

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 uses a specific verb ('Describe') with clear resource ('AWS Organization'). The parenthetical '(master account, feature set, ARN)' effectively distinguishes this from sibling list operations (list_accounts, list_organizational_units) by indicating it returns the organization's own metadata rather than child resources.

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?

No explicit guidance on when to use this versus sibling tools like aws_organizations_list_accounts or aws_organizations_list_roots. While the name implies this retrieves org-level metadata, the description does not clarify relationships between these related operations.

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