AWS MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'List' implies a read-only operation, the description fails to mention pagination behavior (despite the max_results parameter), authentication requirements, or error scenarios when Security Hub is not configured.

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?

The single-sentence description is front-loaded with the action verb, immediately identifies the resource, and uses a brief parenthetical to provide concrete examples without verbosity. Every word serves a purpose.

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 the simple list operation and well-documented schema, the description adequately identifies what is returned (enabled standards with examples). However, lacking an output schema, it misses an opportunity to specify what properties (ARN, status, etc.) are returned for each standard subscription.

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?

The input schema has 100% description coverage for all three parameters (profile, region, max_results). The description does not add semantic details about parameter interactions or formats beyond what the schema already provides, warranting the baseline score.

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 specific verb ('List') and identifies the resource ('security standards enabled in Security Hub'). The parenthetical examples (CIS, AWS Foundational, PCI DSS) effectively distinguish this from sibling tools that handle 'findings', 'hub' configuration, or 'products' by clarifying what constitutes a security standard.

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?

The description provides no guidance on when to use this tool versus alternatives like aws_securityhub_describe_hub or aws_securityhub_get_findings, nor does it mention prerequisites such as Security Hub being enabled in the account.

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