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 states what the tool does but doesn't describe how it behaves: no information about authentication requirements (though parameters suggest AWS auth), rate limits, whether it's read-only or destructive, what the output looks like, or any side effects. The description is minimal and lacks operational context.

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 extremely concise at one sentence with no wasted words. It's front-loaded with the core purpose and doesn't include unnecessary elaboration. Every word earns its place in communicating the essential 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 complexity (6 parameters, AWS authentication), lack of annotations, and 0% schema description coverage, the description is incomplete. While an output schema exists (per context signals), the description doesn't provide enough context about authentication, scope, limitations, or how results are returned. For a security scanning tool with multiple auth parameters, more guidance is needed.

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 provides no information about parameters, while the schema has 6 parameters with 0% description coverage. Parameters like 'region_name', 'profile_name', 'role_arn', and authentication keys are completely undocumented in both schema and description. The description doesn't compensate for the schema's lack of parameter documentation.

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 without default encryption enabled.' It specifies the verb ('find') and resource ('S3 buckets') with a specific condition ('without default encryption enabled'). However, it doesn't explicitly differentiate from sibling tools like 'find_public_s3_buckets' or 'find_unused_s3_buckets' that also target S3 buckets with different criteria.

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 sibling tools like 'find_public_s3_buckets' or 'find_unused_s3_buckets' that might be relevant for different S3 security or optimization scenarios. There's no context about prerequisites, timing, or exclusions.

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