Api task nodes destroy

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no statement about what is destroyed, whether children/cascade data goes with it, or whether the operation requires elevated permissions.

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?

It is short, but this is under-specification rather than conciseness: the entire content is a snake_case identifier with no front-loaded verb or object in natural language. Nothing useful is communicated in the one fragment present.

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, open-world mutation tool with an undocumented identifier parameter and no output schema, the description provides zero of the context an agent needs. It neither describes the target resource nor the consequence of calling it.

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 single required parameter 'id' is undocumented. The description does not say whether this is a task node UUID, a numeric PK, or a ref_id, so it fails to compensate for the schema 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?

The description is the tool slug restated verbatim ('api_task_nodes_destroy'), which only echoes the name and title. The word 'destroy' implies deletion, but nothing states what a task node is or what is removed, and no sibling (e.g. api_task_nodes_partial_update, api_task_nodes_remove_evidence_create) is distinguished.

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?

There is no when-to-use guidance, no precondition (e.g. resolve existing task nodes, detach evidences first), and no mention of alternatives such as partial_update or remove_evidence. An agent has no basis for choosing this over its many siblings.

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