drupal_list_nodes

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

With no annotations, description carries full burden. It mentions pagination, default sort, and flattened attributes but does not disclose rate limits, auth needs, or handling of large results. Basic transparency, not thorough.

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 sentences, no filler, front-loaded with core purpose. Every sentence adds value.

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?

Covers core purpose, pagination, default sort, and flattened attributes. However, no guidance on using filter/sort/fields effectively compared to the query tool. Given schema richness, description is mostly complete but lacks some strategic context.

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 100%, so baseline is 3. Description adds no significant parameter details beyond the schema (e.g., default sort is already in sort param description). Minimal added value.

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 the tool lists nodes by bundle (content type), mentions paginated sets and flattened attributes, and is distinct from siblings like drupal_get_node (single node) or drupal_query_jsonapi (flexible query).

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 over alternatives like drupal_query_jsonapi or drupal_list_taxonomy_terms. The context is clear (list nodes by bundle), but exclusions and comparison are missing.

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