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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds two facts not in the structured data: only published terms are returned (unpublished ones are silently excluded) and each term carries a count. Neither the return shape nor the count semantics (e.g. count of what) is explained, keeping it below a 5.

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?

One sentence, verb-first, zero filler. Both facts it contains (published scope, counts) are load-bearing.

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?

A simple, idempotent read tool with one enum parameter, rich annotations and no output schema. The description covers what is returned at a high level (published terms with counts), which is the only thing the schema and annotations do not already say. Nothing needed to call it correctly is missing.

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 100% and the single 'taxonomy' parameter has an enum, so the schema does the heavy lifting. The description adds no syntax or format detail for the parameter itself; the only extra meaning ('published') is a filter with no corresponding parameter. 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 (list) and resource (taxonomy terms) plus two scoping details: only published terms, and results include counts. It is clearly distinguishable from every sibling, none of which deals with taxonomies. It stops short of naming a sibling to contrast with, but none is a near-duplicate.

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?

There is no guidance on when to reach for this versus search_content or get_schema_context, and no prerequisites or exclusions are stated. Usage is only implied by the word 'list'. An agent must infer that this is the enumeration tool for category/tag/sector/solution values.

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