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 for behavioral disclosure. It mentions what the tool does (finds unused load balancers) and the return format (dictionary), but doesn't disclose important behavioral traits like whether this is a read-only operation, what permissions are needed, whether it makes API calls that incur costs, or how it determines 'no traffic' (e.g., zero requests, zero bytes).

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 perfectly structured and concise: a clear purpose statement followed by well-organized Args and Returns sections. Every sentence earns its place, with no redundant information. The front-loaded purpose statement immediately communicates 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 (7 parameters, AWS integration) and the presence of an output schema (implied by 'Returns' statement), the description is reasonably complete. However, with no annotations and significant behavioral aspects undisclosed (permissions, cost implications, traffic determination method), there are clear gaps that could hinder effective tool selection and invocation.

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, the description compensates well by explaining all 7 parameters in the Args section, providing clear semantics for each (e.g., 'AWS region name', 'Lookback period in days'). It adds meaningful context beyond just parameter names, though it doesn't explain parameter interactions or constraints.

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 with specific verb ('Find') and resource ('load balancers with no traffic'), and distinguishes itself from siblings by focusing on unused load balancers rather than other AWS resources like AMIs, volumes, or functions. It's immediately clear what this tool does.

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 implies usage context through the period parameter (lookback period for traffic analysis) but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided about prerequisites, authentication methods, or how this relates to other cost optimization tools in the sibling list.

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