rm_delete_assignment_subtask

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

The description explicitly notes that the operation is destructive and requires confirm=True, adding meaningful behavior beyond the destructiveHint annotation. This is important because the schema shows confirm defaults to false, so the description clarifies the required flag. It does not describe consequences like cascading deletion, but for a simple delete tool with annotations, this is adequate.

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 one short sentence with no filler and front-loads the core action and the critical destructive flag. Every word contributes useful information.

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 delete tool, the description and annotations together communicate the essential safety requirement (confirm=True). However, it lacks usage context, alternate tool routing, and any detail about what happens after deletion or prerequisites, so an agent has to infer some context from sibling tool names and parameter names.

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%, so the description needed to compensate but only mentions confirm=True. The ID parameters (project_id, assignment_id, subtask_id) are self-explanatory by name, but no format, relationship, or usage details are provided. The confirm parameter receives the only real semantic clarification.

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 specifies a delete operation on 'assignment subtask,' which distinguishes it from sibling tools like rm_delete_assignment. It is concise and uses a specific verb and resource, though it does not explicitly call out the sibling it differs from.

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 rm_delete_assignment or rm_delete_holiday. It only states the action itself, leaving the selection context entirely implied.

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