app_clip_advanced_experience_images__update

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds no extra behavioral context beyond saying 'Update', which aligns with annotations. No contradiction; it simply doesn't add additional nuance (e.g., what fields are affected).

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 one concise sentence plus the HTTP endpoint. It is front-loaded with the action and resource, contains no fluff, and the endpoint adds precise technical context. 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?

Given the tool has 2 parameters, a nested body, and no output schema, the schema covers invocation details. However, the description does not provide additional context about when to use this update (e.g., after uploading an image, updating checksum) or any domain-specific behavior. It is minimally sufficient but not richly complete.

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%: 'id' is described as 'ID from the matching list call' and 'body' as 'JSON:API request body'. The description adds no extra parameter meaning beyond the schema, so baseline of 3 is appropriate.

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 'Update an App Clip advanced experience image' with a specific verb and resource, and includes the HTTP endpoint [PATCH /v1/appClipAdvancedExperienceImages/{id}]. This distinguishes it from sibling create, get, and delete operations on the same resource.

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 implies usage: it is an update tool for App Clip advanced experience images. However, it provides no explicit guidance on when to use it vs. alternatives (e.g., when not to use it, or prerequisites like existing image ID). The purpose is clear, but selection context is minimal.

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