cancel_service_case_resolution

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is covered. The description adds a useful state restriction by specifying 'undecided pre-reply,' but it does not disclose side effects, irreversibility, or downstream consequences of cancellation.

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 concise sentence with no filler, and the action is front-loaded. However, it is under-specified rather than efficiently complete, omitting essential parameter and behavioral context that an agent would need.

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 destructive operation with four required parameters and zero schema description coverage, this description is too thin. It lacks prerequisites, verification steps, reason semantics, and a clear definition of 'undecided pre-reply,' making it unsafe to invoke correctly without external knowledge.

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 description coverage is 0%, and the description does not explain company_ref, project_ref, run_ref, or the nested request.reason field. The word 'exact' hints that run_ref targets a specific run, but no parameter has real semantic guidance, and the reason field is completely undocumented.

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 clearly states a specific verb and resource: cancel a Service run. It also narrows the scope with 'exact undecided pre-reply,' which distinguishes this tool from lifecycle siblings like start_service_case_resolution, get_service_case_resolution, and advance_service_case_resolution. However, 'pre-reply' and 'undecided' are not explained.

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 phrase 'only the exact undecided pre-reply Service run' provides a clear precondition and implies the tool should not be used on decided or replied runs. It does not explicitly name alternatives or advise verifying run state with get_service_case_resolution before cancelling, leaving the guidance partial.

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