AWS MCP Server

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

'Get' implies read-only safety, but with zero annotations provided, the description carries full disclosure burden. It omits error behaviors (e.g., rule not found), AWS credential requirements, or rate limiting details that would help an agent handle failures.

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, front-loaded with action verb, zero redundancy. Appropriate density for the tool's complexity.

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?

Adequate for a read-only describe operation with 4 well-documented parameters, but lacks output format disclosure (no output schema exists) and error handling context that would help interpret results.

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 clear descriptions for all 4 parameters (profile, region, name, event_bus_name). The description adds no parameter-specific semantics beyond the schema, which is acceptable given the high schema coverage, warranting the baseline score.

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?

Clear verb 'Get' and resource 'EventBridge rule' with scope 'full configuration'. However, it does not explicitly differentiate from sibling aws_events_list_rules (which returns summaries) vs this detailed single-rule retrieval.

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 list_rules, or prerequisites like needing the rule name beforehand. Relies purely on AWS API naming conventions being understood by the agent.

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