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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral details: default root path, recursive child-node returns with {id, type, text}, folder vs leaf type semantics, and examples. It omits edge-case behavior like invalid-path handling, but still enriches beyond 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?

The description is three dense sentences: purpose, mechanics, and examples. It is front-loaded with 'Navigate the subject tree,' and every sentence contributes essential information—no filler or redundant repetition of schema fields.

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 tool with one optional parameter, no required fields, and no output schema, the description is remarkably complete. It covers parameter defaults, response structure, node type meanings, and even ties to sibling tools (table_meta/query_table). The only missing detail is behavior on invalid paths, but for this simple read-only navigator, that is a minor omission that does not hinder correct invocation.

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 schema already describes 'path' as a sub-path under /table/, but the description elevates this by explaining it is a node id path, how folder/leaf types determine traversal, and providing concrete examples. This adds meaningful guidance beyond the schema's property description, compensating for any ambiguity in the parameter.

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 opens with 'Navigate the subject tree,' a specific verb+resource pairing that clearly defines the tool's role. It further distinguishes from siblings by explaining the hierarchical path traversal and how leaf table IDs connect to table_meta/query_table, making its unique purpose unmistakable.

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 implicitly provides usage guidance by explaining the path mechanics and giving examples ('' - root, 'be' - Population, 'be05' - Population count tables). It also notes that leaf table IDs are passed to table_meta/query_table, signaling the workflow context, though it does not explicitly say 'use this when...' or exclude other tools.

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