AWS MCP Server

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

No annotations are provided, so the description must carry full disclosure burden. However, it only states the basic operation ('Get') without clarifying if this is read-only (presumed but not guaranteed), what error conditions might arise, rate limits, or the structure/format of the returned stage states. It mentions 'current execution state' but doesn't disclose behavioral traits like data freshness, pagination, or required IAM permissions.

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 consists of a single, efficient sentence with no redundant words. It front-loads the verb ('Get') and immediately specifies the scope ('current execution state of each stage'). Every word earns its place.

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 100% input schema coverage, the parameters are well documented in the structured fields. However, no output schema exists, and the description only briefly mentions what data is retrieved ('execution state of each stage') without describing the return structure, field types, or nesting. For a tool with no annotations and no output schema, more description of the return value would be appropriate.

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?

Schema description coverage is 100%, with all three parameters (profile, region, name) fully documented in the schema. The description adds no additional parameter semantics, but the baseline score of 3 applies when schema coverage is high and sufficient.

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 uses a specific verb ('Get') and clearly identifies the resource ('current execution state of each stage in a CodePipeline'). It implicitly suggests runtime state monitoring versus configuration inspection (distinguishing from 'get_pipeline'), but does not explicitly differentiate from siblings like 'list_pipeline_executions' or clarify when to choose this over other CodePipeline tools.

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 explicit guidance on when to use this tool versus alternatives (e.g., 'get_pipeline' for configuration, 'list_pipeline_executions' for execution history). It does not mention prerequisites like AWS credentials, required permissions, or typical use cases such as troubleshooting failed stages.

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