Delete instant url

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by disclosing that provider scopes, locks and credits apply and that confirmation is required before execution with only one submission allowed -- real operational constraints the annotations do not convey.

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?

Three compact clauses with the method and path front-loaded, then the operational constraints. Every sentence carries information and nothing is padded.

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, non-idempotent delete with no output schema, the description covers the confirmation requirement, single-submission rule, and that scopes/credits apply. It is nearly complete, though it does not state what happens on success or failure, or permissions required for the account parameter.

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 67%, and the description maps {uid} to the DELETE path and ties 'mandatory confirmation' to the confirm flag, adding some meaning. The account parameter's role (workspace profile selection) is left entirely to the schema and is not reinforced in the description.

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?

It states a specific verb and resource via the HTTP route 'DELETE /v5/instant_urls/{uid}', immediately distinguishing it from siblings like get_instant_url and update_instant_url. An agent knows exactly what is deleted without opening the schema.

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?

It adds a real usage constraint -- mandatory confirmation before provider execution and one submission only -- which tells the agent this is a single-shot operation requiring an explicit confirm flag. However, it names no alternatives and gives no explicit when-not-to-use guidance versus get_instant_url or update_instant_url.

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