AWS MCP Server

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

No annotations provided, so description carries full burden. Fails to disclose that this operation may return decrypted secrets requiring special access tokens and explicit acknowledgment (evident from sensitive_access_token, sensitive_access_reason, and sensitive_access_acknowledged parameters). Omits pagination behavior despite max_results parameter.

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 redundancy. However, given the 9 parameters including complex security controls, this brevity borders on under-specification rather than efficient distillation.

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 security-sensitive tool with 9 parameters including explicit sensitive data handling controls. Lacks warnings about audit requirements (sensitive_access_reason), acknowledgment obligations, or AWS-specific pagination behavior.

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 coverage is 100%, establishing baseline 3. Description adds 'path hierarchy' context clarifying the path parameter's purpose, but adds no semantics for the 4 sensitive-access parameters or the interaction between with_decryption and sensitive_access_acknowledged.

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 action (Get), resource (SSM parameters), and mechanism (under a path hierarchy). Distinguishes from sibling aws_ssm_get_parameter by specifying the path hierarchy approach, though lacks explicit contrast with aws_ssm_describe_parameters.

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 siblings like aws_ssm_get_parameter (single parameter lookup) or aws_ssm_describe_parameters. Missing prerequisites like path format requirements (leading slashes) or when decryption is appropriate.

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