app_clip_default_experiences__delete

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

Annotations already provide destructiveHint=true and readOnlyHint=false, and the description merely restates the deletion action without adding extra behavioral context such as irreversibility, cascading effects, or permission requirements. No additional transparency beyond annotations is offered.

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 a single concise sentence that efficiently states the action and includes the REST endpoint. No wasted words or redundant information.

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 simple delete operation with one parameter and well-covered annotations, the description is sufficiently complete. It lacks explicit mention of permanence or side effects, but the destructiveHint annotation covers the key risk, and the schema provides param details.

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% and the id parameter already includes 'ID from the matching list call,' so the tool description adds no new parameter meaning. Baseline for high schema coverage is 3, and the description doesn't compensate further.

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 'Delete an App Clip default experience' with a specific verb and resource, and the REST endpoint is included for clarity. This distinguishes it from sibling tools like get, update, and create for 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 use for deletion, but lacks explicit guidance on when to use versus alternatives. The 'ID from the matching list call' hint provides a prerequisite, but there is no mention of exclusions or comparative context with get/update tools.

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