aws_resource_update

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

Annotations show readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds behavioral context: async by default, returns a ProgressEvent with OperationStatus=IN_PROGRESS and requestToken, and details the polling mechanism. No contradiction with 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?

The description is three sentences long, front-loaded with core purpose. Every sentence adds value: explains the tool, async behavior, and typical patch structure. No wasted words.

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 complexity (10 parameters, async behavior, polling), the description is very complete. It explains default async, optional synchronous mode, patch format, polling parameters, and return value structure. No output schema, but the description sufficiently covers what an agent needs.

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% (all parameters described). The description adds significant meaning beyond schema: explains patchDocument with an example, explains awaitCompletion behavior and related parameters (pollIntervalMs, maxWaitMs, timeoutMs), and mentions ProgressEvent.RetryAfter overriding poll interval.

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 clearly states the tool updates an AWS resource via Cloud Control API using RFC 6902 JSON Patch. It distinguishes from sibling tools like aws_resource_create, aws_resource_delete, aws_resource_get, aws_resource_list, and aws_resource_status. The verb 'Update' and resource 'AWS resource' are specific.

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 explains that the tool is async by default, requiring polling via aws_resource_status, and that passing awaitCompletion: true makes it synchronous. It also provides a typical patch example, guiding when to use this tool versus alternatives.

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