autotask_delete_service_call

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

Adds context beyond annotations: emphasizes irreversibility and the need for user confirmation. Annotations already mark destructiveHint=true, so description complements rather than repeats.

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?

Two concise sentences with a clear warning emoji. No unnecessary words; key points are front-loaded.

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 tool with one parameter and no output schema, the description fully satisfies the need: warns of destructiveness, mentions associated data, and instructs to confirm. No gaps.

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 parameter 'serviceCallId' is adequately described in the schema. Description adds no further parameter details, but 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?

Description explicitly states 'Permanently deletes a service call and all associated data', using specific verb and resource. Distinguishes from sibling delete tools (e.g., autotask_delete_service_call_ticket) via the entity type.

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?

Provides clear instruction to 'Confirm with the user before invoking', which is appropriate for a destructive tool. However, it does not mention alternatives such as update or search, so slightly penalized for missing exclusion guidance.

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