drupal_create_node

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

No annotations provided; description solely states the action and parameter format without disclosing side effects, authentication needs, or return values. Lacks detail on what happens after creation.

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?

Extremely concise: two sentences convey purpose and parameter guidance without unnecessary words.

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?

No output schema exists, and the description does not mention return values or error handling. While it provides some guidance on parameter usage (nested objects), it lacks completeness for a creation tool.

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?

The description adds value by instructing to use 'JSON:API field names' for attributes and relationships, which is not in the schema. The schema's attribute example also clarifies format. However, the 'bundle' parameter lacks explanation.

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 states 'Create a new node,' identifying the verb (create) and resource (node). It distinguishes from sibling tools like drupal_delete_node and drupal_update_node by implying creation of new content.

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 explicit guidance on when to use this tool versus alternatives (e.g., drupal_update_node for existing nodes). The description focuses only on how to pass parameters, not usage context.

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