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 what the tool does but doesn't describe how it works: it doesn't specify what 'no activity' means (e.g., no reads/writes, based on CloudTrail logs), whether it's a read-only operation, what permissions are required, or how results are returned. For a tool with 7 parameters and no annotation coverage, this is a significant gap.

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 with no wasted words. It's front-loaded with the core purpose and efficiently conveys the essential action. Every word earns its place, making it easy to parse quickly.

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 (7 parameters, no annotations, but an output schema exists), the description is incomplete. It doesn't explain the tool's behavior, parameter roles, or typical output. While the output schema may cover return values, the description lacks context on how the tool operates, what 'unused' entails, or authentication requirements, making it inadequate for informed use.

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 mentions 'specified period' which loosely relates to the 'period' parameter, but with 0% schema description coverage and 7 parameters (mostly AWS authentication-related like region_name, profile_name, role_arn), it adds minimal meaning beyond the schema. The description fails to explain what these parameters do or how they affect the tool's behavior, leaving most parameters undocumented.

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 S3 buckets with no activity in the specified period.' It specifies the verb ('Find'), resource ('S3 buckets'), and scope ('with no activity in the specified period'). However, it doesn't explicitly differentiate from sibling tools like 'find_unencrypted_s3_buckets' or 'find_public_s3_buckets', which target different S3 bucket attributes.

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. It doesn't mention prerequisites (e.g., AWS credentials), typical use cases (e.g., cost optimization, security cleanup), or how it differs from other 'find_unused_*' tools for different resource types. 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.