wordpress_list_taxonomy_terms

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

No annotations provided, so description carries full disclosure burden. While 'List' implies read-only, description lacks details on pagination behavior (despite per_page/page params), error handling for invalid taxonomies, or return structure.

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 with no filler. '[UNIFIED]' prefix efficiently signals implementation pattern. However, extreme brevity inadequately services the 6-parameter, 0%-coverage schema.

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 6 parameters with 0% schema coverage and no output schema/annotations, the description is insufficient. It fails to document required 'site' parameter, pagination defaults (100 items), or filtering options (hide_empty, parent) essential for correct invocation.

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%, requiring heavy description compensation. While 'specific taxonomy' implies the taxonomy parameter, the description completely ignores 5 other parameters including required 'site' and pagination controls (per_page, page), providing no syntax or semantic guidance.

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?

States clear verb 'List' and resource 'terms of a specific taxonomy'. Differentiates from sibling tools like wordpress_list_categories/tags by emphasizing it works with 'any registered taxonomy including categories, tags, and custom taxonomies', implying broader scope.

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?

Implies this is the generic option for custom taxonomies by mentioning categories/tags/custom taxonomies together, but lacks explicit guidance on when to prefer this over wordpress_list_categories or wordpress_list_tags specifically.

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