wordpress_get_terms

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

No annotations are provided, so the description carries the full burden. It only states the basic action without disclosing return format, pagination, permissions, or any side effects. For a read operation, more transparency is needed.

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 very concise (one sentence, 9 words) and front-loaded with the action. However, it may be too sparse for effective use.

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 absence of annotations, low schema coverage, no output schema, and many similar sibling tools, the description fails to provide adequate context. It does not explain the concept of terms or how the taxonomy parameter works.

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 description adds some meaning to the 'taxonomy' parameter by listing examples (categories, tags, custom), but does not explain required format, possible values, or defaults. With 0% schema description coverage, this is insufficient but not completely lacking.

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 action (Get terms from a taxonomy) and gives examples of taxonomies (categories, tags, or custom). However, it does not differentiate from sibling tools like wordpress_get_categories or wordpress_get_tags, which could cause confusion.

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?

No guidance on when to use this tool versus alternatives such as wordpress_get_categories or wordpress_get_tags. The description does not provide context for the proper use case.

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