app_clip_default_experiences_delete_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 nothing: not that the operation is destructive/irreversible, not what related resources (localizations, header images) are affected, not the required auth scope or role. Only the verb 'DELETE' hints at mutation.

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?

Very short, but the content is duplicated — the identical endpoint string appears twice, once outside and once inside parentheses. That duplication is pure noise with no informational value, so length is minimal but not earned.

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 destructive one-parameter operation with no annotations and no output schema, the agent still lacks the information needed to invoke it safely: what gets deleted, side effects on dependent resources, and required permissions. The endpoint path alone is not sufficient context.

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% and the single 'id' parameter is documented in the schema as 'the id of the requested resource'. The description adds no format, source, or constraint information beyond that, so the baseline 3 for high-coverage schemas applies.

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 is the tool name restated as a raw REST route: 'DELETE /v1/appClipDefaultExperiences/{id}', repeated verbatim in parentheses. It conveys the HTTP verb and resource path but never explains in plain language what an App Clip default experience is or what deleting one means. Precise-but-tautological, which the rubric places at 2.

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 when-to-use guidance, no prerequisite (e.g. whether the experience must be unreleased first), and no mention of sibling alternatives such as app_clip_default_experiences_get_instance or _update_instance. The DELETE verb implies the operation is for removing an existing experience, but nothing is stated.

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