AWS 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 mentions specific data retrieved (admins, create defaults) but omits critical behavioral details such as authorization requirements, rate limits, whether the operation is read-only (implied but not stated), or what format the response takes.

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 with the main action front-loaded. However, given the absence of annotations and output schema, the brevity leaves significant gaps in behavioral context that could have been addressed with additional clauses.

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 lack of annotations and output schema, the description meets minimum viability by identifying the target resource and exemplifying the returned data. However, it fails to compensate for missing structured data by describing return formats, pagination behavior, or error conditions expected from this AWS API call.

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 baseline score is 3. The description adds context about what 'settings' entails (admins, defaults) but does not elaborate on parameter semantics beyond what the schema already documents for profile, region, and catalog_id.

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 clear verb ('Get') and resource ('Lake Formation data lake settings'), and enumerates specific setting types ('admins, create defaults'). It implicitly distinguishes from sibling tools like aws_lakeformation_list_permissions by focusing on configuration settings rather than access permissions, though it could be more explicit about scope differences.

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 contains no guidance on when to use this tool versus alternatives (e.g., when to use this instead of aws_lakeformation_list_permissions or list_resources), nor does it mention prerequisites such as requiring Lake Formation administrative privileges or specific IAM permissions.

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