Delete TAP async job

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description only restates the deletion concept. It does not explain whether the job is cancelled if running, whether deletion is permanent, or what happens on repeated deletion attempts, so it adds no behavior beyond the annotations.

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 short sentence with the verb 'Delete' front-loaded and no wasted words. It is concise, though it largely repeats the title and could have used the space to include behavioral or usage context.

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?

The schema fully covers parameters and annotations cover the destructive profile, so basic invocation is sufficiently supported. However, the description is thin on when to use the tool and what deletion actually entails, leaving the agent to infer important selection context from the tool name and sibling names alone.

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 fully documents all three parameters, including the url/service alternatives and jobIdOrUrl format, with 100% coverage. The description adds no parameter-level detail, 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 uses a specific verb, 'Delete', names the exact resource, 'TAP async job', and notes the remote scope. This clearly differentiates it from sibling tools that submit, query, wait, or fetch jobs.

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 gives no explicit guidance on when to use deletion versus alternatives like job_status, job_wait, or job_fetch, and no preconditions are stated. The appropriate usage is only implied by the verb 'Delete'.

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