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 implies a read-only operation ('Get') and specifies account-level scope and inclusion of 'subscription status' (billing context). However, it omits permission requirements, failure modes (e.g., if Security Hub is not enabled), or rate limit concerns.

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 of appropriate length. Front-loaded with the action verb 'Get'. No redundant or filler text; every word earns its place.

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?

For a simple 2-parameter describe operation with no output schema provided, the description adequately indicates the return value scope (configuration and subscription status). Given the low complexity and complete schema coverage, it is sufficiently complete.

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?

Input schema has 100% description coverage (profile and region are well-documented in the schema). The description adds no semantic information about parameters beyond what the schema provides, warranting the baseline score of 3.

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 verb 'Get' and resources 'Security Hub configuration and subscription status' clearly. However, it does not explicitly differentiate from sibling tools like aws_securityhub_get_findings which retrieve different data types (findings vs hub 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 no guidance on when to use this tool versus alternatives such as the finding-related or standards-related Security Hub siblings. No prerequisites, failure conditions, or 'see also' references are mentioned.

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