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

With no annotations supplied, the description carries the full burden: it makes clear this is a non-destructive enumeration over a fixed dataset vocabulary, which is meaningful behavioral context. However, it says nothing about the shape or size of the response (one value list per taxonomy?), whether results are static, or whether pagination applies.

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?

Two short sentences with the resource and its enumerated categories front-loaded, followed by the intended purpose. The only blemish is the slightly garbled phrase "filtering taxonomy matching," which could be tightened to something like "matching filter values."

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?

For a simple zero-parameter read tool with no output schema, the description is adequate: it names the dimensions available. What it omits is whether the call returns the permissible values for each dimension versus just the dimension names, which is the key ambiguity an agent would face when deciding how to use the result.

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 no parameter semantics to explain; the baseline of 4 applies. The description correctly adds no noise about arguments, consistent with the empty input schema.

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 and resource ("List all taxonomies") and enumerates the concrete taxonomy families returned (industries, seniority levels, education levels, company sizes), so an agent knows exactly what domain metadata this exposes. It does not explicitly contrast itself with siblings like list_cities or list_roles, which is the only thing keeping it from a 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?

"Use this to ensure accurate filtering taxonomy matching" implies the tool should be called before constructing filtered queries, but it never states a concrete when-to-use condition, an ordering against siblings, or any when-not-to-use case. The guidance is suggestive rather than actionable.

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