wp_list_terms

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

With no annotations, the description carries the burden of explaining side effects. It explicitly states 'Read-only' and provides a notable behavioral nuance: the parent field returns None for flat taxonomies, contrasting with WordPress's 0 for top-level. It does not detail error cases, but this is sufficient for a read-only list operation.

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 concise and well-structured. It front-loads the core purpose, lists returned fields, and then expands on the taxonomy and search parameters. The parent None vs 0 explanation is valuable and not verbose, adding clarity without unnecessary length.

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?

Although there is no output schema, the description indirectly outlines the return structure (id, name, slug, parent, post count) and explains an important edge case. It does not mention pagination, sorting, or error responses, but for a straightforward read-only list tool, the information provided is sufficient for basic 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?

The description explains taxonomy (a slug from wp_list_taxonomies) and search (optional simple filter on term name), but does not explain the 'install' parameter at all. Since the schema provides no parameter descriptions, this gap leaves a required parameter undefined, limiting the agent's ability to correctly invoke the tool.

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 purpose: listing terms in a taxonomy, and enumerates the fields returned (id, name, slug, parent, post count). It also clarifies the taxonomy parameter, making the intended use unambiguous even without annotations.

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 a prerequisite (requires REST transport) and explains that search is an optional filter. It does not explicitly compare with sibling tools like wp_list_taxonomies or wp_create_term, but the read-only nature and simple listing behavior are clear enough for an agent to decide when to invoke it.

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