wp_list_taxonomies

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

With no annotations, the description carries the behavioral burden. It clarifies a meaningful behavioral trait: only public taxonomies are returned, and object types are included. The verb 'List' also implies a read-only operation, though the description does not explicitly state that no changes are made or mention any auth/rate-limit considerations.

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 a single, efficient sentence with no filler. It front-loads the verb and resource, then adds the only key qualifier ('public' and 'with object types').

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?

For a no-parameter list operation without an output schema, the description covers the essential information: what is listed (taxonomies), the scope (public), and what is included (object types). It omits details like ordering or exact return representation, but these are minor for such a simple tool.

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 input schema has zero parameters, so the baseline is 4. The description's mention of 'public' and 'object types' relates to output scope rather than parameter semantics, so no additional parameter guidance is needed.

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 uses a specific verb ('List') and names a precise resource ('all public WordPress taxonomies') with a useful detail ('with object types'). This clearly differentiates it from sibling tools like wp_list_taxonomy_terms, wp_list_categories, and wp_list_post_types.

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 usage is implied: use this when you need the full list of public taxonomies. However, there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives such as wp_list_taxonomy_terms for terms within a taxonomy, leaving the agent to infer selection from the name and description alone.

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