AWS MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It adds valuable domain context explaining that access points have 'path and permissions' attributes and serve as 'application-specific entry points,' which helps the agent understand the resource model. However, it lacks operational details such as pagination behavior, throttling considerations, or default result limits.

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?

Single efficient sentence with zero waste. Parenthetical content adds essential context without clutter. Information is front-loaded with the action verb, making it immediately clear this is a list operation.

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?

For a read-only list operation with 100% parameter schema coverage and no output schema, the description is reasonably complete. It appropriately explains the conceptual nature of access points (application-specific entry points) which aids resource identification, though it could benefit from noting pagination behavior implied by max_results.

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?

Input schema has 100% description coverage with clear documentation for all four parameters (profile, region, file_system_id, max_results). With high schema coverage, baseline 3 is appropriate; the description does not need to repeat parameter details already well-documented in the schema.

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?

Description uses specific verb 'List' with resource 'EFS access points' and parenthetically defines what they are (application-specific entry points with path and permissions). Clearly distinguishes from siblings aws_efs_describe_file_systems and aws_efs_describe_mount_targets by specifying the distinct resource type and its characteristics.

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?

Description provides no guidance on when to use this tool versus alternatives, nor does it explain filtering strategies (e.g., when to use file_system_id parameter vs listing all). No prerequisites or contextual conditions are specified.

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