AWS MCP Server

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

No annotations are provided, yet the description fails to disclose behavioral traits: it doesn't state this is read-only/safe, doesn't mention AWS API pagination behavior (critical for list operations), and doesn't describe what data is returned (deployment IDs vs full objects) since no output schema exists.

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 of 10 words is front-loaded with the core action. While efficient and free of redundancy, it is arguably too terse given the lack of annotations and output schema—every word earns its place but leaves significant gaps.

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 no annotations and no output schema, the description carries a heavy burden that it fails to meet. For a 5-parameter AWS list operation, it should mention pagination, return value structure (e.g., 'returns deployment IDs'), or permission requirements. As written, it covers only the basic filtering capability.

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%, establishing baseline 3. The description mentions filtering by 'application' and 'status' which maps to parameters, but adds no semantic clarification beyond the schema (e.g., doesn't explain that 'profile' is for AWS credential selection or that all filters are optional).

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 'List' and resource 'CodeDeploy deployments' clearly. Mentions 'filtered by application and status' which hints at scope, but fails to explicitly distinguish from sibling 'aws_codedeploy_get_deployment' (singular vs plural) or clarify that this returns a list/IDs rather than detailed objects.

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 explicit guidance on when to use this tool versus alternatives like 'aws_codedeploy_get_deployment'. While 'optionally filtered' implies parameters are not required, it lacks prerequisites, exclusion criteria, or workflow guidance for an agent deciding between listing deployments versus getting a specific one.

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