list_nodes

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

There are no annotations, so the description carries the full burden. 'Lista' implies a read-only operation, and pagination and filtering are mentioned, but the description does not disclose return format, default pagination values, or potential side effects. This is adequate but not rich.

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?

A single, compact sentence that front-loads the main action and resource, then adds the two relevant features. No redundant or filler 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?

For a simple read-only list tool this is adequate, but with no output schema it would benefit from describing what kind of node data is returned and what the default pagination behavior is. The essentials are present, but an agent may be unsure about the result shape.

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 50%; contentType and filterTitle are documented in the schema, while pageSize and pageOffset are not. The description mentions 'paginación' and 'filtro opcional por título', which partially compensates by hinting at the purpose of those parameters, but it does not explain offset semantics or how pagination maps to the specific parameters.

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 identifies the action ('Lista'), the resource ('nodos'), and the scope ('de un content type del sitio Drupal'). It also mentions the key features, pagination and optional title filter, which distinguishes it from sibling tools like get_node (single node) and list_resource_types (content types).

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 description provides clear context for when to use this tool: when listing nodes of a specific content type. It does not explicitly state exclusions or mention alternatives, so it misses the top tier, but the use case is strongly implied by the wording.

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