create_node

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

With no annotations provided, the description carries the behavioral transparency burden. It reveals a meaningful prerequisite: mcp_agent must hold creation permission for the specific content type. It does not mention return format, failure modes, or that the call mutates Drupal content, leaving behavioral disclosure incomplete.

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 short sentences, with the action first and the permission caveat second. Every word adds value; there is no boilerplate or repetition of schema structures.

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 three parameters, nested objects, and no output schema, the description is thin: it lacks error/result behavior, how to discover valid content types, and when to use this tool with relationships. The permission caveat helps, but the agent still has to infer several operation-critical details.

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 JSON:API formatting examples for attributes and marks relationships as optional, which is useful beyond the bare schema. The required contentType parameter still has no description in either the schema or the description text, so a key semantic gap remains.

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 states a concrete operation: 'Crea un nodo nuevo en el sitio Drupal' (create a new node). This verb+resource pair makes it clearly distinct from sibling read/list/update tools, even though it does not explicitly name them.

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 creation intent is clear, and the permission requirement ('Requiere que el usuario mcp_agent tenga permiso de creación en ese content type') gives useful context. However, there is no explicit when-to-use vs. update_node/list_nodes guidance or any exclusion criteria; the agent must infer the typical workflow.

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