AWS MCP Server

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

Annotations indicate this is a non-readOnly, non-destructive, non-idempotent, open-world operation. The description adds no behavioral context beyond this—it doesn't explain what 'authorize' does operationally (e.g., adds rules, may affect network traffic), rate limits, or authentication needs. No contradiction with annotations.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, though it lacks detail due to brevity.

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 complexity (2 parameters with nested objects, 50% schema coverage, no output schema, and non-readOnly operation), the description is inadequate. It doesn't explain the tool's purpose in depth, parameter usage, or behavioral implications, leaving gaps for an AI agent to invoke it correctly.

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 50%, with complex nested parameters. The description adds no parameter semantics—it doesn't explain what 'SecurityGroupArgs' contains or how to structure IP permissions. It fails to compensate for the low schema coverage, leaving key parameters like 'DryRun' or 'TagSpecifications' unexplained.

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 states the action ('authorize') and resource ('security group egress') but is vague about what 'authorize' entails—it doesn't specify that this adds outbound traffic rules. It distinguishes from sibling 'authorize-security-group-ingress' by mentioning 'egress', but lacks detail on scope or effect.

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 guidance on when to use this tool versus alternatives like 'modify-security-group-rules' or 'revoke-security-group-egress'. The description only mentions the region context without usage context, prerequisites, or exclusions.

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