AWS FinOps 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 states the tool gets recommendations but doesn't explain what kind of recommendations (e.g., resize, delete, modify), whether it requires specific AWS permissions, if it's read-only or mutative, or what the output format looks like. For a cost optimization tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence: 'Get recommendations for optimizing NAT Gateway costs.' It's front-loaded with the core purpose and wastes no words. Every part of the sentence contributes directly to understanding the tool's function.

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's moderate complexity (cost optimization with 6 parameters) and the presence of an output schema, the description is minimally adequate. The output schema likely covers return values, reducing the need for output details in the description. However, with no annotations and poor parameter documentation, the description leaves gaps in behavioral and parameter context that could hinder effective tool use.

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 description mentions no parameters, while the schema has 6 parameters with 0% description coverage. The schema titles (e.g., 'Region Name', 'Profile Name') provide basic labels, but the description adds no semantic context about what these parameters mean, their relationships, or how they affect the recommendations. With low schema coverage, the description fails to compensate.

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 recommendations for optimizing NAT Gateway costs.' It specifies the verb ('Get recommendations') and resource ('NAT Gateway costs'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_all_cost_optimization_recommendations' or 'find_unused_nat_gateways', which would require a 5.

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 prerequisites, timing, or how it relates to sibling tools such as 'get_all_cost_optimization_recommendations' or 'find_unused_nat_gateways'. Without any usage context, the agent must infer when this specific NAT Gateway optimization tool is appropriate.

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