beta_app_clip_invocations__delete

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

Annotations already declare destructiveHint=true and idempotentHint=true, covering the key behavioral traits of a delete operation. The description adds only the endpoint, not additional behavioral context. With annotations present, the description meets the minimum bar but does not enrich beyond the structured data.

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 sentence plus the endpoint. Every word serves a purpose with no filler or repetition. It is as concise as possible while conveying the action.

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 well-described parameter and annotations covering safety and idempotency, the description is complete. No output schema is needed, and the agent has all necessary information to invoke the tool correctly.

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?

The schema provides 100% coverage with a clear description for the only parameter 'id' ('ID from the matching list call'). The tool description adds nothing about parameters, but the schema fully compensates, so the 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 states exactly what the tool does: it deletes a beta App Clip invocation. The verb+resource is specific and clearly distinguishes it from sibling operations like get, update, and create 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?

Usage is implied by the verb 'Delete' and the endpoint, but there is no explicit when-to-use guidance, prerequisites, or alternatives mentioned. It is adequate for a straightforward delete operation but lacks any additional context about when deletion is appropriate.

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