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

Annotations already declare readOnly/idempotent/non-destructive, and 'read-only, runs straight away' merely repeats them. The valuable additions are the scoping constraint that only public taxonomies are returned (private ones excluded) and the disclosure of what fields come back, which goes beyond the annotations.

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 the purpose and return fields in one compact sentence, followed by two short clarifiers. The parenthetical site marker is redundant with the schema and slightly noisy, keeping it from a 5.

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 zero-required-parameter read tool with no output schema, the description covers what is returned (slug, label, hierarchical flag, attached post types) and the public-only filter, which is everything needed to call and interpret it correctly.

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?

Single optional parameter with 100% schema coverage and an enum, so the schema fully documents site_id. The description only gestures at the site via '(site: demo.royalplugins.com)', which duplicates the schema; baseline 3 applies.

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 a specific verb and resource ('Get all registered public taxonomies') and clarifies scope ('built-in plus custom ... like product_cat, brand'), plus what is returned. It does not name or differentiate from sibling taxonomy-listing tools (mcp-easy-ai__wp_get_taxonomies, emcp-tools-list-taxonomies), so it falls short of a 5.

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?

Usage is only implied — an agent infers this is a discovery/introspection call to run before term operations. There is no explicit when-to-use/when-not or mention of alternatives such as wp_get_post_types or wp_get_terms, so guidance is minimal.

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