AWS MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate that this is a read-only/safe operation, does not describe pagination behavior (despite the limit parameter implying it), and does not hint at the return structure or AWS-specific behaviors like throttling.

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 extremely concise at 9 words in a single sentence. Every word earns its place with the action verb front-loaded. No redundancy or noise is present.

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 simple 4-parameter schema with complete coverage and no nested objects, the description is minimally adequate. However, with no output schema and no annotations, it lacks hints about the return value structure (log group ARNs, creation dates, etc.) and safety characteristics that would complete the picture.

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?

With 100% schema description coverage, the baseline is 3. The description mentions 'optional prefix filter' which maps to the log_group_prefix parameter, but this adds only marginal value beyond the schema's own description ('Filter by log group name prefix'). No additional semantic context is provided for profile, region, or limit parameters.

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 verb (List) and resource (CloudWatch Log groups) and mentions the key filtering capability (prefix filter). However, it does not distinguish from sibling tools like aws_logs_filter_log_events or aws_logs_get_log_events, which operate on log events rather than log groups.

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 mentions the 'optional prefix filter' capability, but provides no explicit guidance on when to use this tool versus sibling alternatives (e.g., when to list groups vs. when to retrieve events from a specific group). No prerequisites or exclusions are stated.

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