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

Beyond the readOnly, idempotent, and non-destructive annotations, the description discloses the traversal source (GLEIF), the aggregation behavior (every entity sharing the root), and a non-obvious default filter (pension/retirement trusts excluded). No contradiction with annotations.

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 tightly written sentences that front-load the core behavior and then add a meaningful default-filter detail. No filler or redundant restatement of the title.

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?

The description sufficiently explains what the tool returns and the default filter for a hierarchy-walking function, even without an output schema. Pagination behavior is left to the schema; additional detail about result item shape or no-root cases would be nice but is not essential.

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?

Schema coverage is 60%, with lei/domain/per_page described. The description adds meaning to include_pension_trusts by noting the default exclusion, and reinforces the subject-resolution concept. Page remains undescribed in both schema and description, but the overall parameter intent is reasonably clear.

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 concrete action ('Walk the GLEIF ultimate-parent hierarchy') and result ('return every entity sharing the same conglomerate root'), naming both the resource and scope. This clearly distinguishes it from broad sibling tools like company_search or company_timeline.

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?

The description implies when to use the tool—when you need the full corporate family under a conglomerate root—and adds the default exclusion of pension/retirement trusts. However, it does not explicitly state when to prefer this over alternatives or when not to use it.

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