get_node

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

With no annotations available, the description carries the full burden of disclosing behavior. 'Obtiene' clearly marks this as a read/retrieval operation rather than a mutation, which is useful. However, it does not disclose return value format, error behavior, permissions, or whether related fields are included.

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?

The description is a single focused sentence with no filler, and the key retrieval intent is front-loaded. It is concise and readable, though slightly too minimal to cover the full parameter context.

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?

This tool has no output schema, no annotations, and a 0% parameter schema coverage, so the one-line description must do more. It fails to explain the contentType parameter, the expected return value, or how this retrieval tool differs from sibling retrieval tools, making it incomplete for reliable agent use.

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 for the bare input schema. It gives meaning to the uuid parameter ('por su UUID'), but it says nothing about the required contentType parameter, leaving half of the required inputs unexplained.

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 specific verb and resource: it retrieves a single Drupal node by UUID. This clearly distinguishes get_node from siblings like list_nodes (which lists many nodes) and create_node/update_node (which mutate nodes).

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 phrase 'por su UUID' implies the tool should be used when a specific UUID is known, but the description does not explicitly say when to prefer it over list_nodes or other retrieval tools. It provides no exclusions or alternative routing guidance.

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