wordpress_list_taxonomy_terms

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

With no annotations, the description only says 'list terms', but fails to disclose pagination behavior, error handling (e.g., invalid taxonomy), or performance implications, which are essential for a listing tool.

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 efficient with three sentences front-loading purpose, but could be improved by structuring parameter hints briefly.

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, no output schema, and many sibling tools, the description lacks important details on pagination, filtering, and return values, making it incomplete for proper tool usage.

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% and the description does not explain any of the 6 parameters (e.g., page, per_page, parent, hide_empty), leaving the agent with no guidance beyond the schema.

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 terms of a specific taxonomy, with examples including categories, tags, and custom taxonomies, distinguishing it from siblings like wordpress_list_categories and wordpress_list_tags.

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 for any taxonomy but does not explicitly state when to use this tool over alternatives or when not to use it, leaving usage guidance implicit.

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