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

Beyond the readOnly/idempotent/destructive annotations, the description discloses that no auth is required, specifies the underlying data source (andmed.stat.ee PXWeb API), and explains the two kinds of returned nodes (type=l categories and type=t table descriptors). This is genuinely useful behavioral context.

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?

The description is dense and front-loaded, with every major piece of information earning its place. It loses a point for slight redundancy with the schema's path description and for an imprecise self-reference to 'estonia-statistics.catalog' instead of the actual tool name.

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 single-optional-parameter catalog browser with an output schema and strong annotations, the description is complete: it covers how to start, how to navigate, what node types to expect, where the data comes from, and what to use next. Nothing essential 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?

Even though schema coverage is 100%, the description adds real meaning to the single path parameter: it defines empty-string behavior, enumerates valid top-level path values, and prescribes the recursive navigation strategy. This goes well beyond the bare schema definition.

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 states a specific verb ('browse'), a clear resource ('Statistics Estonia's statistics database tree'), and the mechanism ('by path'). It also distinguishes the tool from the sibling table_metadata tool by stating that leaf nodes lead to estonia-statistics.table_metadata.

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?

Explicit guidance is provided: use empty path to get top-level databases, navigate recursively until type=t nodes appear, then switch to estonia-statistics.table_metadata. This directly tells an agent when to use this tool and when to hand off to an alternative.

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