AWS MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Retrieve' implying read-only safety, but fails to disclose pagination behavior (critical for CloudWatch logs), result ordering (forward/backward), or error handling when streams don't exist.

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?

Two short sentences with no filler. The first states purpose, the second states requirements. Zero waste and appropriately front-loaded.

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?

With 7 parameters, no output schema, and no annotations, the description is insufficiently complete. It omits critical operational context such as pagination handling (despite the presence of a 'limit' parameter), timestamp behavior, and differentiation from filtering alternatives.

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%, with all 7 parameters fully documented. The description mentions the two required parameters specifically, adding emphasis but no additional semantic context (syntax, format examples, or value constraints) beyond the schema definitions.

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 a clear verb ('Retrieve') and resource ('log events from a specific CloudWatch log stream'), identifying the scope accurately. However, it fails to distinguish from sibling tool 'aws_logs_filter_log_events', which also retrieves log events but supports cross-stream filtering and pattern matching.

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 only states the prerequisite ('Provide both log_group_name and log_stream_name'), which restates required schema parameters. It provides no guidance on when to use this tool versus 'aws_logs_filter_log_events' or other alternatives.

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