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

readOnlyHint=true already tells the agent this is a safe read, but the description adds semantic context beyond that: what 'public' means ('false = terms classify content but have no pages of their own') and what 'fabrement' marks ('created here'). These clarify the meaning of returned data in a way annotations cannot.

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?

Structure is good: resource first, field list second, workflow instruction last. The parenthetical clarifications for 'public' and 'fabrement' earn their space by adding meaning, though the sentence is dense enough that it flirts with over-packing.

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?

With a readOnly annotation and an existing output schema, the description needn't explain return structure, yet it still summarizes the fields helpfully. Combined with the pre-creation workflow guidance, an agent has what it needs to invoke this correctly.

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 takes zero parameters, so there is nothing to document at the argument level and the baseline is 4. The field list describes output shape rather than inputs, which is complementary but not required given an output schema exists.

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 names the resource (taxonomies on this site) and enumerates the returned fields, making clear it is a read/inventory operation. The verb is only implicit in the description text (carried by the title 'List taxonomies'), so it falls just short of a self-contained verb+resource statement, but there's no ambiguity with siblings.

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?

It gives explicit workflow guidance: 'Call before create-taxonomy (reuse what exists) and before create-term,' which tells the agent when to reach for it and why. It stops short of naming when not to use it or comparing against list-terms, so it is strong but not fully exhaustive.

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