AWS MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate this is read-only, omits pagination behavior (critical for AWS Describe* APIs), error conditions, or return value structure. 'Describe' implies read-only but explicit confirmation would help.

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 brief at 4 words with no redundancy. However, given zero annotations and 4 optional parameters, the brevity leaves significant gaps in agent guidance that a longer description could fill.

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?

With no output schema, no annotations, and 4 optional filtering parameters, the description should disclose return structure, pagination limits, or service-specific constraints. It provides none of this behavioral context.

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% with all 4 parameters well-documented. The description adds no parameter-specific guidance (e.g., when to combine filters with db_cluster_identifier), establishing baseline 3 per scoring rules for high-coverage schemas.

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 the verb (Describe) and resource (DocumentDB clusters) clearly, decoding 'docdb' to 'DocumentDB'. However, it fails to distinguish from sibling aws_docdb_describe_db_instances (clusters vs instances) or aws_rds_describe_db_clusters (RDS vs DocumentDB), leaving ambiguity for agents selecting between similar tools.

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, when to use db_cluster_identifier versus filters, or any prerequisites. The description is purely declarative with no operational context.

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