Projects Delete Assignment Subtask

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

Annotations already declare destructiveHint=true and non-idempotency, so the 'Destructive' label is largely redundant. The description does add real value beyond the annotations by disclosing the confirm=True gate, which is not inferable from the hints. It says nothing about cascade effects on children, reversibility, or permission requirements.

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?

A single short sentence with the action and the critical guard clause front-loaded; nothing is padded. The only minor waste is restating 'Destructive', which the annotations already encode.

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?

An output schema and annotations are present, so return values and safety profile are covered elsewhere. For a destructive, three-ID hierarchical operation, however, the definition omits the parent/child relationship semantics and any consequence of deletion, leaving an agent to guess at the blast radius.

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 must compensate, and it only explains the confirm parameter. project_id, assignment_id and subtask_id receive no semantic detail such as accepted ID types, whether the subtask must belong to that assignment, or hierarchy requirements.

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+resource (delete an assignment subtask), which is clearly separable from the sibling projects_delete_assignment and projects_delete_project_phase because of the 'subtask' qualifier. However, it never explicitly names or contrasts with those siblings, so the differentiation is inferential rather than stated.

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 one operational rule that matters — confirm=True is required for this destructive call — is given, which is genuine when-to-use guidance. There is no guidance on when to delete a subtask versus updating it, nor on parent/child entity state or alternatives.

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