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

Annotations already declare readOnly, idempotent, non-destructive. The description adds valuable behavior: needs edit_posts, non-public taxonomies appear only for accounts that may assign their terms, takes no arguments, and it's forwarded to one site. This is meaningful context beyond annotations, though return format detail is already partly covered.

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?

Front-loaded with purpose and return shape; dense but every sentence carries information. The trailing forwarding note and permission detail are slightly crammed into one block but still earn their place.

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?

Complete for a zero-param list tool with no output schema: it documents the return structure, permission requirement, visibility rule for non-public taxonomies, and scope (single site via bridge). Nothing an agent needs to call it correctly is missing.

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?

Zero parameters, so baseline is 4. The description reinforces this ('takes no arguments') and explains the return fields (name, label, objects) and how name maps to the taxonomy argument of term tools — useful semantic bridging.

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?

Specific verb+resource: 'List the taxonomies registered on the site', with built-in category and post_tag explicitly included. It clearly distinguishes itself from wp_list_terms (which lists terms) and wp_get_post_types (which lists 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?

Names the alternative tools and their roles: terms are listed by wp_list_terms, post types by wp_get_post_types, and this tool supplies the taxonomy value those tools consume. Effectively tells the agent when this tool is the right one.

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