tenki_delete_preview_url

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds value by stating the result is 'permanently offline', which conveys irreversibility. This aligns with and reinforces the annotations without contradicting them.

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?

A single concise sentence with no wasted words. The action verb leads, and the permanently-offline consequence is included without padding.

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, single-parameter delete operation, the description plus annotations and schema provide everything an agent needs: what is deleted, how it is identified, and that the action is destructive and permanent. No output schema is needed for this tool.

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 input schema has 100% parameter coverage, with preview_url_id already described as 'The preview URL id to delete.' The description's 'by id' adds no new meaning beyond the schema, so the baseline of 3 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 uses a specific verb ('Delete'), a specific resource ('preview URL'), and an explicit scope ('by id'), making it immediately clear what the tool does. It also distinguishes itself from siblings like tenki_get_preview_url and tenki_unbind_preview_url by emphasizing permanent deletion.

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 makes the purpose and consequence clear enough that an agent can infer when to use it: when a preview URL should be permanently removed. It does not explicitly contrast with related tools like tenki_unbind_preview_url or tenki_touch_preview, so it misses the top score for explicit alternatives and exclusions.

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