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. It states the tool finds tables with no activity but doesn't explain how it determines this (e.g., based on CloudWatch metrics, over what timeframe, what constitutes 'no activity'). It omits details like whether it requires specific IAM permissions, if it's read-only or has side effects, or how results are returned. For a tool with 7 parameters and no annotation coverage, this is a significant gap in 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 a single, clear sentence: 'Find DynamoDB tables with no read/write activity.' It's front-loaded with the core purpose, has zero waste, and is appropriately sized for a simple statement. Every word earns its place by conveying the essential action and target.

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 complexity (7 parameters, no annotations, but has an output schema), the description is incomplete. It states what the tool does but doesn't cover behavioral aspects like authentication needs (implied by parameters like 'access_key'), how 'no activity' is defined, or any constraints. While the output schema may handle return values, the description lacks sufficient context for safe and effective use, especially with no annotations to fill gaps.

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?

The description adds no meaning beyond the input schema, which has 0% description coverage (no parameter descriptions in schema). With 7 parameters (e.g., 'region_name,' 'period,' 'profile_name'), the description doesn't explain what they do, how they affect the search, or their relationships (e.g., that 'period' likely defines the days to check for activity). This leaves parameters undocumented and fails to compensate for the low schema coverage.

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: 'Find DynamoDB tables with no read/write activity.' It specifies the verb ('find'), resource ('DynamoDB tables'), and criteria ('no read/write activity'). However, it doesn't explicitly differentiate from sibling tools like 'find_underutilized_dynamodb_tables' or 'find_overutilized_dynamodb_tables,' which would require mentioning specific thresholds or usage patterns.

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 DynamoDB (e.g., 'find_underutilized_dynamodb_tables,' 'find_overutilized_dynamodb_tables,' 'analyze_dynamodb_throttling'), there's no indication of how this tool differs in context or when it's preferred. It lacks any mention of prerequisites, exclusions, or typical scenarios for application.

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