kaiten_delete_sd_service

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

No annotations are present, so the description carries the burden of disclosing behavior. The 'archive' qualifier is useful because it signals that deletion is not necessarily a permanent hard delete. However, it does not mention permissions, side effects on related requests or SLAs, reversibility, or what the response contains.

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, front-loaded sentence with no filler. Every word adds meaning, and the key action and resource are immediately clear.

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?

Given the low complexity of a one-parameter delete operation, the description is minimally adequate. But with no annotations and no output schema, it could still disclose more about what archiving entails, whether deletion cascades, and any admin or permission requirements. It is not incomplete enough to prevent a call, but it leaves notable 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?

The schema fully documents service_id with 100% coverage, so the baseline is 3. The description helps by clarifying that the 'service' in question is a 'Service Desk service,' but it adds no additional format, validation, or contextual constraints beyond the schema.

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 a specific verb ('Delete') and a specific resource ('Service Desk service'), and the parenthetical '(archive)' clarifies the exact semantic of the operation. This clearly distinguishes it from sibling delete tools targeting other resources like sd_requests, sd_sla, or sd_organizations.

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 guidance on when to use this tool versus alternatives such as kaiten_update_sd_service or kaiten_delete_sd_request. An agent must infer that this is the tool for removing an entire service, and no prerequisites or exclusions are mentioned.

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