kaiten_delete_sd_request

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds a useful caveat: the call may return 405 and deletion may only be available via the Service Desk portal. However, it does not mention whether deletion is permanent, whether special permissions are required, or what a successful response looks like.

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 two sentences with no filler. The action is front-loaded, and the 405/portal caveat is a valuable, non-obvious detail that earns its place.

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 is reasonably complete: it names the resource, the schema documents the required parameter, and it flags a key failure mode. It could be more complete with permission or success-response details, but the low complexity keeps this from being a significant gap.

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 already fully documents the only parameter, request_id, with a description and integer type. The tool description adds no additional parameter-level detail, so it meets the baseline but does not exceed it.

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 and resource: 'Delete a Service Desk request.' This clearly distinguishes the operation from sibling SD tools like kaiten_update_sd_request, kaiten_get_sd_request, and the various other delete_* tools, which target different resources.

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 verb 'Delete' implies when to use this tool, and the note about a possible 405 and portal-only availability hints at a fallback path. However, it does not explicitly state when to prefer this tool over alternatives like kaiten_update_sd_request, nor does it provide clear when-not-to-use conditions.

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