wordpress_get_taxonomies

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only states the action ('get all registered taxonomies') without describing what data is returned (e.g., full taxonomy objects vs. names), whether any filtering is applied, or any side effects. The lack of detail beyond the basic operation is a gap.

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, focused sentence with no filler or redundant information. It is front-loaded and immediately states the purpose. Perfectly concise for a tool of this simplicity.

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 tool's simplicity (no parameters, no output schema), the description is mostly sufficient but misses a few details that would make it complete: it does not specify the return format or whether any filters/ordering exist. With siblings like 'wordpress_get_taxonomy' and 'wordpress_get_terms', a brief note on relationship could improve completeness, but the core functionality is adequately covered.

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 tool has zero parameters, and the schema is empty (coverage 100% by default). The baseline for 0 params is 4, and the description correctly does not invent any parameter details. Since there are no parameters to document, the description offers sufficient semantics by clarifying the scope ('all registered').

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 'Get all registered taxonomies' uses a specific verb ('Get') and resource ('taxonomies'), clearly distinguishing it from the sibling tool 'wordpress_get_taxonomy' (singular) by specifying 'all registered'. It is immediately clear what the tool does.

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 provides no guidance on when to use this tool versus alternatives such as 'wordpress_get_taxonomy' or 'wordpress_get_terms'. There is no mention of context, prerequisites, or exclusions. The usage is only implied by the tool name and generic description.

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