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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing about read-only nature, recursion depth, pagination, or what the result contains. Only the word "hierarchy" hints that the response is tree-structured.

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?

It is a single front-loaded phrase with no waste, but that brevity comes at the cost of under-specification rather than efficient communication.

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?

No annotations, no output schema, and zero parameter documentation mean the description should explain substantially more; as written, an agent cannot reliably construct the call or anticipate the return shape.

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 single required parameter parent_id has 0% schema description coverage, and the description never mentions it, its expected format, or what value denotes the root. The word "hierarchy" weakly implies a parent-child linkage, but the agent is left guessing how to obtain a valid parent_id.

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?

"Explore Polish statistical subject hierarchy" names the resource (Polish statistical subject hierarchy) but uses a vague verb ("explore") instead of stating that it lists subjects — presumably children of a given parent. It does not distinguish itself from siblings like list_units or get_statistics.

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 call this versus get_statistics, get_unit, or list_units, nor any note about preconditions or entry-point behavior. The agent must infer usage purely from the tool name.

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