AWS MCP Server

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

No annotations are provided, yet the description discloses almost no behavioral traits. It does not mention pagination behavior (despite max_results parameter implying it), return format, credential requirements beyond the schema, or the read-only nature of the operation.

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?

While brief, this represents under-specification rather than effective conciseness. The single sentence fails to earn its place by providing value beyond the tool name itself. Critical information about scope, pagination, and return values is absent.

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?

Without an output schema, the description should explain return values and pagination behavior. It also omits mention that zero parameters are required, which is important for a list/filter operation. Given the tool's purpose, the description fails to provide sufficient context for effective agent 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 a baseline of 3. The description implies the purpose of the max_results parameter (listing), but adds no semantic value regarding parameter relationships (e.g., region override behavior) or syntax details beyond what the schema already documents.

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 'List SageMaker notebook instances' is tautological, essentially restating the tool name (aws_sagemaker_list_notebook_instances). It fails to distinguish this tool from siblings like aws_sagemaker_list_endpoints or aws_sagemaker_list_training_jobs, which also list SageMaker resources.

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 (e.g., when to list notebook instances vs. endpoints or training jobs). Does not mention that all parameters are optional, which is important context for a filtering list operation.

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