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 disclosure. It adequately indicates this is a read operation via 'Get' and specifies what data is returned, but lacks details on return format, authentication requirements, or what happens if the pipeline name doesn't exist.

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 of 10 words. Every word earns its place—'full structure' and 'stage configuration' are specific and non-redundant. Front-loaded with the action verb. No waste.

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?

Acceptable for a retrieval tool with 100% input schema coverage. The description indicates what content is returned ('structure and stage configuration'), compensating somewhat for the missing output schema. However, lacks return format details or pagination notes that would help the agent process the response.

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 has 100% description coverage (profile, region, name all documented), establishing baseline. The description mentions 'CodePipeline' which contextualizes the 'name' parameter, but adds no syntax details, formatting requirements, or examples 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: 'Get' is a clear action verb, 'CodePipeline' identifies the resource, and 'full structure and stage configuration' precisely scopes what is retrieved. This clearly distinguishes from sibling tools like get_pipeline_state (which returns execution state) and list_pipelines (which returns summaries).

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 guidance provided on when to use this tool versus siblings like list_pipelines (which should be called first to discover pipeline names) or get_pipeline_state. No prerequisites or error handling mentioned.

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