AWS MCP Server

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

No annotations provided, so description carries full burden. It successfully discloses critical security behaviors: secrets are exposed in conversation plaintext and the tool requires write access (blocked in readonly). Missing only error handling behavior and return structure details.

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?

Three sentences with zero waste: purpose statement, security warning, and operational constraint. Perfectly front-loaded with the action verb, followed by critical cautions. No redundant or filler 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?

Given high security sensitivity and lack of output schema, the description appropriately prioritizes disclosure of exposure risks and mode restrictions. Could be improved by noting retrieval failures (e.g., 'returns error if secret not found'), but adequately complete for safe invocation.

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 does not add parameter-specific guidance (e.g., ARN format hints, version precedence rules), but the schema already comprehensively documents all five parameters including examples.

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 specific verb 'Retrieve' with specific resource 'actual secret value', clearly distinguishing it from sibling tools 'describe_secret' (metadata) and 'list_secrets' (inventory) by emphasizing it returns the sensitive payload, not just configuration.

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 explicit cautionary context ('Use with caution — the value will appear in the conversation') and operational constraint ('Blocked in --readonly mode'). Lacks explicit comparison text like 'For metadata only, use describe_secret instead', though the word 'actual' implies this distinction.

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