Delete change request task

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description usefully adds the error behavior (MissingParameterError, ParameterError on bad params/deserialization) and the return shape, which is genuine added context, but it says nothing about cascading effects or confirmation requirements despite being destructive.

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 docstring boilerplate badly mismatches the schema: it documents two params while twenty exist, and repeats type information (:type:, :rtype:) that adds no value. The first line is well front-loaded, but the rest is verbose filler rather than useful content.

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, 22-parameter tool with no output schema and 0% schema coverage, the description is materially incomplete: it omits which task identifier actually takes effect (task_sys_id vs change_request_task_sys_id) and gives no return-value detail beyond 'parsed Pydantic model'. An agent could easily pass the wrong parameter.

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% across 22 parameters, yet the description documents only two (change_request_sys_id, task_sys_id). The other twenty parameters, including the more relevant change_request_task_sys_id, are left entirely uninterpreted, so the description fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Delete a task associated with a change request'), which is clear and distinguishable from siblings like delete_change_request and update_change_request_task. It does not explicitly name sibling tools or scope limits, so it falls short of a 5.

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?

No guidance on when to use this versus delete_change_request, delete_table_record, or update_change_request_task. No prerequisites (permissions, state constraints) are given; the agent must infer usage entirely.

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