wp_list_taxonomies

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

With no annotations, the description carries the full burden and does disclose read-only behavior plus transport and visibility constraints. It does not mention error conditions or return envelope details, but the core behavioral expectations are clearly communicated.

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 compact and front-loaded with the main purpose, then adds essential usage and constraint details in three sentences. No filler or redundant phrasing.

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 simple list operation and lack of output schema, the description covers the key output fields, the relationship to term tools, and operational constraints. It is slightly incomplete only because the install parameter is unexplained, but overall context is strong.

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 only parameter, install, has no schema description and the tool description does not explain it at all. Since schema coverage is 0%, the description should compensate, but it provides no guidance on what install means or how to specify it.

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?

Clearly states the tool lists a site's taxonomies and names the key returned fields (slug, name, rest_base, hierarchical, post types). It also distinguishes its role as the starting point for term tools by explaining the returned slug is used as the taxonomy parameter elsewhere.

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?

Explicitly says to 'start here' and explains that the slug returned is what every other term tool expects as the taxonomy parameter. It also notes important constraints: only taxonomies with show_in_rest appear, and the tool requires the REST transport rather than the wpcli/SSH gateway.

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