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 but only implies read-only behavior via 'Get'. It fails to disclose what specific status information is returned (e.g., IsLogging boolean, latest delivery times), error conditions, or AWS permission requirements.

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 is efficient and front-loaded with the core action. However, extreme brevity contributes to informational gaps rather than clarity.

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?

Inadequate for a tool with no annotations and no output schema. The description omits critical context about return value structure, what 'logging status' specifically entails in AWS CloudTrail, and how this differs from the describe operation.

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?

Input schema has 100% description coverage, establishing baseline 3. The description adds minimal semantic value beyond the schema, merely mentioning 'CloudTrail trail' which aligns with the 'name' parameter. No elaboration on optional profile/region 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?

States specific verb (Get) and resource (logging status for a CloudTrail trail), but fails to distinguish from sibling aws_cloudtrail_describe_trails. The distinction between 'describing' a trail and getting its 'logging status' is subtle and unexplained.

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?

Provides no guidance on when to use this tool versus alternatives like aws_cloudtrail_describe_trails or aws_cloudtrail_lookup_events. No mention of prerequisites, permissions, or typical usage patterns.

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