drupal_list_taxonomy_terms

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

With no annotations, the description carries full burden. It reveals the default sort order ('weight') but omits other important behaviors such as pagination behavior, response format, permission requirements, or limits. The description is insufficient for an agent to fully understand the tool's side effects or constraints.

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 extremely concise with two sentences that are front-loaded. Every word adds value without repetition or fluff. It efficiently conveys the core purpose and a key behavioral detail (default sort).

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?

Given the absence of an output schema and the presence of a nested filter parameter, the description does not adequately prepare an agent. It fails to explain the return structure, any pagination, the format of the filter object, or the maximum limit. The context from sibling tools is not leveraged.

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 stating the default sort value, which clarifies the 'sort' parameter meaning beyond the schema (which lacks a description for sort). However, the 'limit' parameter has no description, and the 'filter' parameter's complex structure is not elaborated. The schema coverage is 50%, and the description partially compensates.

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's action: 'List terms in a vocabulary' with a specific verb and resource. It provides examples of valid vocabularies ('category', 'tags'), and is distinct from sibling tools which deal with nodes and users.

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 implies usage via examples of common vocabularies but does not explicitly state when to use this tool over alternatives or when not to use it. No exclusion criteria or alternative tool references are given.

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