app_clip_advanced_experience_images_create_instance

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no auth/scope requirements, no note that this is a mutating create with side effects, no status/response behavior, and no constraints on the image payload. The pointer to the OpenAPI request schema is a useful structural breadcrumb but is not behavioral disclosure.

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?

It is short and front-loads the endpoint, but the route is duplicated verbatim in parentheses ("POST /v1/appClipAdvancedExperienceImages (POST /v1/appClipAdvancedExperienceImages)"), which is pure waste, and the remaining text is a schema pointer rather than usable content.

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?

For a mutating create tool with a nested JSON:API envelope object, no annotations, and no output schema, the description should at least summarize the required envelope/attributes. Instead it defers entirely to an external OpenAPI component, leaving an agent unable to construct a valid call without that spec.

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 effectively 100% (the single body parameter points at components.schemas.AppClipAdvancedExperienceImageCreateRequest), so the baseline is 3. The description repeats that same schema reference without adding field-level meaning, so it neither helps nor hurts beyond the baseline.

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 names the HTTP verb (POST) and the resource path (appClipAdvancedExperienceImages), so an agent can infer this creates an advanced-experience image record. However, it only restates the endpoint rather than stating the purpose in domain terms, and it gives no way to distinguish this from app_clip_advanced_experience_images_get_instance or _update_instance beyond the verb echo in the route.

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?

There is no statement of when to use this tool, no prerequisites, and no mention of alternatives among the many sibling create/update/get tools. The only implicit signal is the POST endpoint, which an agent could infer from the name alone.

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