AWS 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. While 'Get' implies a read-only operation, the description does not confirm safety, disclose potential AWS API rate limits, mention costs, or describe error conditions (e.g., function not found).

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, efficient sentence of nine words with no redundancy. It is appropriately front-loaded with the action verb. However, it is minimally informative rather than richly so, stopping short of providing usage context or behavioral details that would make it exemplary.

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?

The description adequately indicates what the tool retrieves ('configuration and metadata') despite the absence of an output schema. However, given the lack of annotations and the complexity of AWS API operations, it lacks guidance on authentication requirements, regional considerations, or error handling that would make it 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 100% schema description coverage, the structured fields already clearly define 'profile', 'region', and 'function_name'. The description does not add parameter-specific semantics, syntax guidance, or usage examples beyond what the schema provides, warranting the baseline score of 3.

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 provides a specific verb ('Get') and resource ('Lambda function') with clear scope ('detailed configuration and metadata'). It implicitly distinguishes from sibling tools like 'aws_lambda_list_functions' (list vs. get single) and 'aws_lambda_invoke' (retrieve vs. execute), though it doesn't explicitly reference siblings in the text.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus 'aws_lambda_list_functions' (for discovery) or 'aws_lambda_invoke' (for execution), nor does it mention prerequisites like AWS credentials or required IAM permissions.

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