AWS MCP Server

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

No annotations provided. While the description mentions SecureString decryption, it critically omits the out-of-band approval token requirement, audit reason requirements (sensitive_access_* params), and error cases. No mention of what the return value contains.

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?

Two sentences with zero redundancy. However, extreme brevity is inappropriate given the security-sensitive nature and complex authorization workflow implied by the parameter schema.

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?

Security-sensitive secret retrieval tool with 7 parameters including complex authorization controls, no annotations, and no output schema. Description under-describes the security access workflow and prerequisites necessary for safe 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?

Schema coverage is 100%, establishing baseline 3. Description mentions SecureString decryption which contextualizes the with_decryption boolean, but adds no guidance on the four sensitive_access_* security parameters or their relationships.

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) and resource (SSM parameter value) with key behavioral detail (SecureString decryption). Does not distinguish from sibling aws_ssm_get_parameters_by_path which retrieves multiple parameters by path.

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 single-parameter getter versus batch alternatives, nor explains that sensitive_access_token and related parameters are required for accessing decrypted secrets.

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