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 partially compensates by describing what information is returned (status, duration, error info), but fails to disclose that this is a read-only operation, requires AWS credentials, or mention any rate limiting considerations.

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 a single, efficient sentence of nine words with a precise parenthetical summary of return values. It is appropriately front-loaded with no redundant or wasted text.

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?

While the description mentions key return fields to compensate for the missing output schema, it lacks completeness regarding behavioral safety (read-only status) and does not reference the hierarchical relationship to other CodeDeploy operations (applications → deployment groups → deployments).

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 structured schema already fully documents all three parameters (profile, region, deployment_id). The description adds no parameter-specific semantics beyond what the schema provides, warranting the baseline score of 3.

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 uses a specific verb ('Get') with clear resource ('CodeDeploy deployment') and specifies what details are returned (status, duration, error info). However, it does not explicitly differentiate from the sibling 'aws_codedeploy_list_deployments' or clarify this retrieves a single deployment by ID versus a list.

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 provides no guidance on when to use this tool versus alternatives like list_deployments first to obtain a deployment ID, nor does it mention prerequisites such as needing a valid deployment ID from a prior listing or create operation.

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