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. While 'Get' implies a read operation, the description doesn't mention authentication requirements, rate limits, data freshness, or what the recommendations include (e.g., coverage period, savings estimates). For an AWS cost tool with 6 parameters, this leaves significant 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 that directly states the tool's purpose without unnecessary words. It's appropriately sized for what it communicates, though it could benefit from additional context.

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 of AWS cost recommendations, 6 undocumented parameters, no annotations, and many similar sibling tools, the description is insufficient. While an output schema exists (which helps), the description doesn't address authentication, parameter usage, or differentiation from alternatives, leaving the agent with inadequate guidance.

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%, meaning none of the 6 parameters have descriptions in the schema. The tool description provides no information about any parameters, failing to compensate for the complete lack of schema documentation. Parameters like 'profile_name', 'role_arn', and authentication credentials remain unexplained.

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 action ('Get') and resource ('Savings Plans recommendations from AWS Cost Explorer'), making the tool's purpose understandable. However, it doesn't differentiate from sibling tools like 'get_reserved_instance_recommendations' or 'get_all_cost_optimization_recommendations' that also provide AWS cost optimization recommendations.

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. With many sibling tools focused on AWS cost optimization (e.g., 'get_reserved_instance_recommendations', 'get_all_cost_optimization_recommendations'), there's no indication of how this tool differs in scope or when it's the appropriate choice.

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