AWS FinOps 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 only states what the tool does at a high level without mentioning permissions needed, whether it's read-only or destructive, rate limits, output format, or how 'no traffic' is determined. This is inadequate for an 8-parameter tool with AWS authentication parameters.

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 that gets straight to the point with zero wasted words. It's appropriately sized for the tool's purpose and front-loads the core functionality.

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 complexity (8 parameters, AWS authentication, no annotations) and the presence of an output schema, the description is incomplete. While the output schema may cover return values, the description doesn't address critical context like authentication requirements, what constitutes 'no traffic', or how this tool fits into the broader optimization workflow with sibling tools.

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?

With 0% schema description coverage for 8 parameters, the description fails to compensate. It mentions 'specified period' which relates to the 'period' parameter, but doesn't explain the other 7 parameters including authentication details (profile_name, role_arn, access_key, etc.), region selection, or result limits. The description adds minimal value beyond the schema.

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 verb ('find') and resource ('NAT Gateways') with a specific criterion ('with no traffic in the specified period'). It distinguishes from siblings like 'find_unused_elastic_ips' by focusing on NAT Gateways, but doesn't explicitly differentiate from other 'find_unused_*' tools beyond the resource type.

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, prerequisites, or typical use cases. It doesn't mention sibling tools like 'get_nat_gateway_optimization_recommendations' that might be related, leaving the agent with no contextual usage information.

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