aws_resource_diff

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

Annotations already indicate readOnly (true), destructive (false), idempotent (true). Description adds that it fetches current state and simulates in memory, which is useful but not critical beyond annotations.

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?

Three sentences, no wasted words, front-loaded with purpose and key differentiator.

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?

Despite no output schema, description explains return format (before/after, changed paths) and limitations (operation subset). All parameters documented via schema, context signals confirm 100% coverage.

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 coverage is 100%, so description adds minimal value. It mentions supported operations (add/remove/replace) which is already in schema enum; no additional parameter details.

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 clearly states it is a dry-run simulation of a CCAPI update, fetching current state and returning before/after with changed paths. Distinguishes from sibling aws_resource_update.

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?

Explicitly advises using this before aws_resource_update to verify patches, and notes that move/copy/test operations should go directly to aws_resource_update.

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