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

Annotations already declare the operation read-only, open-world, idempotent, and non-destructive. The description goes beyond those by naming the upstream data source, stating that no auth is required, and revealing the has_variables leaf marker; it omits rate-limit or pagination behavior, though pagination is already documented in the schema.

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?

Every sentence earns its place: purpose, root-vs-child navigation, leaf-to-variables routing, and data source/auth. The key usage instructions are front-loaded before source details, with no filler.

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 an optional-parameter browse tool, the definition is complete: output schema covers return shape, annotations cover safety, and the description covers navigation, source, and the next sibling to call. Nothing needed to invoke it correctly 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?

All three parameters are described in the schema, including parent_id's omit-to-root behavior and concrete examples, and the description mostly restates that. Since schema coverage is 100%, the prose adds little parameter-level meaning beyond reinforcing the parent_id semantics.

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: 'Browse the topic hierarchy' of Poland's GUS Local Data Bank. It lists representative domains and then separates this navigation tool from gus-poland.variables by stating that leaf subjects are passed to that sibling tool.

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 provides exact selection logic: omit parent_id to get the 33 root topics, pass parent_id for children, and route leaf subjects to gus-poland.variables. This tells an agent both when to call the tool and what to do after the result, which is more than most sibling definitions provide.

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