AWS FinOps MCP Server

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose authentication requirements (though parameters suggest AWS credentials), rate limits, whether it's read-only or has side effects, or what format the recommendations come in. This is inadequate for a tool with 7 parameters and no annotation coverage.

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 with zero wasted words. It's appropriately sized for a tool with an output schema and gets straight to the point without unnecessary elaboration.

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?

The description states the core purpose adequately, and the existence of an output schema means return values are documented elsewhere. However, for a tool with 7 parameters, 0% schema description coverage, and no annotations, the description should provide more context about authentication, scope, and usage to be complete.

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 0%, so the description must compensate but provides no parameter information. It doesn't explain what 'region_name', 'service', or the various AWS credential parameters mean in context, or which are required versus optional. With 7 undocumented parameters, this creates significant ambiguity for the agent.

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 ('Get') and resource ('Reserved Instance purchase recommendations') with source ('from AWS Cost Explorer'). It's specific about what the tool retrieves, but doesn't explicitly differentiate from sibling tools like 'get_savings_plans_recommendations' or 'analyze_reserved_instance_utilization' which are related but distinct.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, timing considerations, or how this differs from other cost optimization tools in the sibling list. The agent must infer usage from the tool name alone.

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