drupal_delete_node

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

Highlights irreversibility, which is critical behavioral info, but doesn't disclose permissions, side effects (e.g., cascading deletes), or confirmation behavior. With no annotations, the description partially fulfills transparency needs.

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?

Two succinct sentences with front-loaded purpose and a key behavioral note. No redundant or extraneous 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 simple delete operation, the description covers essential info: what it does and that it's irreversible. Could mention existence precondition or return value, but given no output schema, it's reasonably complete.

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 coverage is 0%, so description must compensate. It explains that bundle and UUID identify the node, adding meaning beyond raw schema names. However, it doesn't clarify bundle's meaning (content type) or UUID format, leaving some ambiguity.

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?

Description clearly states the verb (delete), resource (node), and required identifiers (bundle + UUID). It distinguishes from sibling tools like drupal_create_node or drupal_update_node.

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 tool versus alternatives (e.g., drupal_update_node, drupal_get_node). The agent receives no context about prerequisites or exclusions.

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