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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only operation and conveys that the tool returns a set of vocabularies, but it does not disclose details such as whether results are paginated, sorted, or include metadata. For a simple tool this is adequate but not especially rich.

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 clean, single sentence that front-loads the action and resource, then lists the scope with no filler. Every element contributes meaning; no wasted words.

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 has no parameters, no output schema, and no annotations, the description covers the essential information: what the tool lists and the specific vocabularies it returns. It lacks explicit return-format detail, but for a zero-parameter listing tool it is close to complete.

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, so the input schema is trivially 100% covered. The baseline for zero parameters is 4, and the description does not need to explain any argument semantics; nothing is missing here.

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 uses a specific verb ('List') and resource ('taxonomies'), and enumerates the exact vocabulary types covered (category, capability, audience, pricing, platform, ownership, relationship). This clearly distinguishes it from sibling tools like get_resource or search_resources, which serve different lookup operations.

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 implies the tool is for retrieving taxonomy vocabularies, but it does not explicitly state when to use this over siblings or provide any alternatives. The context of a no-parameter listing tool makes the use case fairly obvious, yet there is no direct guidance.

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