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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the exact shape of the returned node and its children, plus the default root behavior when id_or_path is omitted. It doesn't mention depth limits or invalid-path error behavior, which keeps it at 4.

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?

Three tight sentences: purpose, return shape, then routing guidance. The behaviorally important detail (omit id_or_path → top concepts) is front-loaded alongside the core purpose.

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?

With no output schema, the description correctly compensates by listing returned fields, and the zero-required-parameter default is made explicit. The remaining gap is the undocumented language parameter and no indication of pagination or traversal depth.

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 only 50%: id_or_path is documented in the schema, but the 'language' parameter has no description anywhere and the description never mentions it, leaving its accepted values and effect undocumented. The description essentially restates the schema's id_or_path text rather than compensating for the gap.

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?

States a specific verb+resource ('Navigate the PTPGE hierarchy') and enumerates the returned fields (id, notation, label, level, elementType, hasChildren). It also distinguishes itself implicitly from ptpge_search_terms by framing itself as systematic exploration rather than keyword search.

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 for systematic exploration instead of guessing search keywords' gives a clear positive use case and contrasts with search-style siblings, and 'Omit id_or_path to get the three top concepts' defines the entry point. It never names ptpge_search_terms explicitly as the alternative, so there is a small inference step.

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