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 valuably discloses the content of the returned history (steps, errors, I/O), but lacks operational disclosures: does not state this is read-only, requires Step Functions read permissions, or describe pagination behavior beyond the max_results parameter.

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 sentence, front-loaded with zero waste. Every clause earns its place: main clause defines action/resource, parenthetical clarifies specific data returned. Appropriately sized for the tool's complexity.

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?

With no output schema, the description partially compensates by describing return content (steps, errors, I/O). However, it omits mention of the event structure format, pagination behavior, and that this is a read-only operation. Given 100% schema coverage and clear scope, it is reasonably complete but not exhaustive.

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, establishing baseline 3. The description mentions 'execution' which loosely maps to execution_arn, but adds no syntax guidance, format details, or semantic relationships between parameters beyond what the schema already provides.

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?

Excellent specificity: verb 'Get' + resource 'event history of a Step Functions execution' + scope clarification '(steps, errors, inputs/outputs)'. Clearly distinguished from sibling 'describe_execution' (which returns metadata) by emphasizing granular 'event history' with specific payload details.

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 explicit 'when to use vs alternatives' guidance provided. However, the parenthetical content '(steps, errors, inputs/outputs)' implies a debugging/auditing use case distinct from high-level status checks, offering implied usage context without explicit directiv

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