AWS CDK 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. It states the tool 'gets prescriptive CDK advice' but doesn't describe what form this advice takes (e.g., text, structured data), whether it requires authentication, rate limits, or any side effects. The mention of 'ctx: MCP context' in the Args section is redundant with the input schema and doesn't add behavioral context.

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 description is reasonably concise with two sentences, but the second sentence ('Args: ctx: MCP context') is redundant given the empty input schema and doesn't add value. The first sentence clearly states the purpose, but overall structure could be improved by removing the unnecessary Args reference.

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 tool has no parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., text advice, structured recommendations), how comprehensive the guidance is, or any limitations. For a guidance-providing tool with zero structured metadata, more behavioral context is needed.

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 tool has 0 parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to compensate for any parameter documentation gaps. The Args section mentioning 'ctx: MCP context' is unnecessary but doesn't detract significantly from the baseline score for a parameterless tool.

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 clearly states the tool's purpose: 'get prescriptive CDK advice for building applications on AWS.' This specifies both the verb ('get') and resource ('prescriptive CDK advice'), though it doesn't explicitly differentiate from sibling tools like 'ExplainCDKNagRule' or 'GetAwsSolutionsConstructPattern' which also provide CDK-related guidance.

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. It doesn't mention any prerequisites, exclusions, or specific contexts where this tool is preferred over sibling tools like 'ExplainCDKNagRule' or 'SearchGenAICDKConstructs', leaving the agent to infer usage from the general purpose statement alone.

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