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 explains what the tool does (finds unused log groups) and describes the return format ('Dictionary with unused log groups'), but doesn't cover important behavioral aspects like authentication requirements (beyond listing credential parameters), error handling, rate limits, or what constitutes 'unused' beyond the period parameter. The description provides basic operational context but lacks comprehensive behavioral transparency.

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 well-structured with clear sections (purpose, Args, Returns) and front-loads the core functionality. Every sentence serves a purpose, though the parameter explanations could be slightly more concise. The structure helps the agent quickly understand the tool's purpose and parameters without unnecessary verbosity.

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 (8 parameters, no annotations, but has output schema), the description provides good coverage. It explains the purpose, documents all parameters, and describes the return format. The output schema existence means the description doesn't need to detail return values extensively. However, it could benefit from more context about authentication methods and error scenarios to be fully 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?

With 0% schema description coverage, the description compensates well by providing clear explanations for all 8 parameters. Each parameter gets a brief but meaningful description that adds value beyond the schema (e.g., 'Lookback period in days', 'Maximum results to return', 'AWS profile name (optional)'). The description effectively explains what each parameter means and how it affects the tool's behavior, though it doesn't provide format details or validation rules.

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 specific action ('Find CloudWatch Log Groups with no recent log events'), identifies the resource ('CloudWatch Log Groups'), and distinguishes from siblings by focusing on unused log groups rather than other AWS resources. It provides a precise verb+resource combination that is immediately understandable.

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 parameter explanations (e.g., 'Lookback period in days'), but doesn't explicitly state when to use this tool versus alternatives. There's no mention of prerequisites, related tools, or specific scenarios where this tool is most appropriate. The guidance is limited to what can be inferred from the parameter descriptions.

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