wordpress_list_taxonomies

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

No annotations are provided, so the description must carry the full burden. It mentions returning 'configuration and post type associations' but does not disclose behavioral traits such as read-only nature, required permissions, or potential performance impacts. The implicit read-only nature of 'list' is not made explicit.

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 sentence that front-loads the main action. However, the '[UNIFIED]' prefix is unnecessary and could cause confusion. Otherwise, it is concise and to the point.

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 simplicity of the tool (one parameter, no output schema), the description is minimally adequate. It specifies what is returned but lacks detail about the structure of 'configuration and post type associations'. It does not compensate for the missing parameter documentation.

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 schema has one required parameter 'site' with 0% description coverage. The description does not explain the 'site' parameter or its expected format (e.g., URL). It adds no value beyond the schema, leaving the agent to infer meaning from context.

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 verb 'list' and the resource 'registered taxonomies', including both built-in and custom. It also specifies what is returned ('configuration and post type associations'). Among many sibling 'wordpress_list_*' tools, this uniquely identifies its focus on taxonomies.

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 does not explicitly state when to use this tool versus alternatives like 'wordpress_list_taxonomy_terms' or 'wordpress_list_categories'. Usage is implied by the tool's name and purpose, but no guidance on exclusions or context is provided.

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