wordpress_get_terms

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

No annotations are provided, so the description carries full burden. It states 'Get terms' which implies a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, pagination, or what happens on errors. For a tool with no annotations, this is insufficient to inform the agent about how it behaves beyond the basic action.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and includes helpful examples in parentheses. Every word earns its place, making it easy to parse quickly.

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 no annotations, 0% schema coverage, no output schema, and 1 parameter, the description is incomplete. It lacks details on return values, error handling, authentication, and usage context. For a tool in a complex WordPress environment with many siblings, this minimal description leaves significant gaps for an agent to operate effectively.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'taxonomy' as a parameter and gives examples ('categories, tags, or custom'), but doesn't explain the format, allowed values, or how to specify custom taxonomies. With 1 parameter and no schema details, the description adds minimal semantics beyond the parameter name.

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 'Get' and resource 'terms from a taxonomy', specifying examples like 'categories, tags, or custom'. It distinguishes from siblings like 'wordpress_get_categories' or 'wordpress_get_tags' by being more generic. However, it doesn't explicitly contrast with these specific siblings, so it's not a perfect 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?

The description provides no guidance on when to use this tool versus alternatives like 'wordpress_get_categories' or 'wordpress_get_tags'. It mentions 'taxonomy' but doesn't explain scenarios where this generic tool is preferred over specific ones. No exclusions or prerequisites are stated.

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