aws_executeExecute AWS service operations with required safety confirmation to manage infrastructure changes.
Execute AWS operations (requires appropriate safety mode)
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | ||
| service | Yes | ||
| operation | Yes | ||
| parameters | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does 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 only hints at safety mode but does not describe side effects, confirmation flow, or response format. The confirm parameter is not mentioned, leaving a significant transparency gap for an execution tool.
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 short and front-loaded with the purpose, but it is under-specified rather than concise. It omits essential context, making it not appropriately sized for a tool with 4 parameters and no schema descriptions.
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 tool's complexity (4 params, no annotations, no schema descriptions), the description is grossly incomplete. It doesn't explain what operations can be executed, how safety mode gates execution, or what the output looks like, even though an output schema exists.
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 0%, so the description must compensate. It does not mention service, operation, parameters, or confirm at all, offering no help to the agent in understanding what to pass.
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 states a verb and resource ('Execute AWS operations') but is generic and does not differentiate from many sibling tools that also operate on AWS, such as aws_query or validate_operation. It lacks specificity about what operations are covered.
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?
It mentions a prerequisite ('requires appropriate safety mode') but provides no guidance on when to use this tool versus alternatives. There are no exclusions or conditions directing the agent to a more specific sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.