AWS MCP Server

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

No annotations are provided, so the description carries full disclosure burden. While 'Get' implies read-only, it does not explicitly confirm safety, disclose authentication requirements (beyond the profile parameter existing), mention rate limits, or describe what specific configuration details (MFA settings, password policies, etc.) are included in the response.

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?

Extremely concise at 7 words and a single sentence. No redundancy or filler. However, it may be overly terse given the lack of annotations and output schema, suggesting room for one additional sentence of behavioral context without sacrificing clarity.

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?

Adequate for a standard AWS 'describe' operation with well-documented parameters, but minimal given no output schema or annotations. It does not describe the return value structure or content, leaving the agent to infer what 'detailed configuration' encompasses.

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%, with all three parameters (profile, region, user_pool_id) fully documented in the schema. The description adds no additional parameter semantics (syntax examples, format constraints), warranting the baseline score of 3 for high schema coverage.

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 clear verb ('Get') and specific resource ('Cognito user pool'), stating exactly what is retrieved ('detailed configuration'). However, it misses the opportunity to explicitly distinguish from sibling 'aws_cognito_list_user_pools' (this fetches one specific pool by ID vs listing all pools).

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?

No guidance provided on when to use this versus the 'list_user_pools' sibling, nor any mention of prerequisite requirements (e.g., needing a valid user_pool_id from a list operation first). The description stands alone without contextual usage hints.

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