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 that this is a read-only operation, whether results are paginated (typical for AWS List APIs), or what occurs if the application_name does not exist. The agent has no safety signals beyond the verb 'List'.

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 with no redundant text or filler. The action verb is front-loaded. However, the extreme brevity leaves significant gaps in behavioral and contextual information that should be included for an AWS API tool.

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?

No output schema exists, yet the description fails to indicate what data is returned (deployment group names, ARNs, etc.). Missing pagination behavior disclosure common to AWS list operations. Sibling tools exist that perform similar functions, but no hierarchical relationship is explained.

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%, documenting profile, region, and application_name. The description mentions 'for a CodeDeploy application' which aligns with the application_name parameter but does not add semantic meaning, constraints, or format details beyond what the schema already provides.

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 clear verb 'List' with specific resource 'deployment groups' scoped to a CodeDeploy application. Differentiates from siblings like list_applications and list_deployments by specifying the correct AWS resource type (deployment groups vs applications/deployments).

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 list_applications or get_deployment. Does not clarify that an existing application_name is required (from list_applications) before invoking this tool.

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