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

Annotations already declare read-only and safe operation. The description adds meaningful behavioral context by explaining the tree structure and the distinction between folder ('l') and table ('t') entries, which helps the agent interpret results.

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 two sentences, front-loaded with the main action, and contains no wasted words.

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 simple one-parameter navigation tool, the description covers the core behavior including entry types and root behavior. It could mention response shape or error cases, but it is sufficient given the annotations and simple schema.

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 input schema provides full coverage for the 'path' parameter with a clear description and examples. The tool description reiterates path behavior but adds little beyond what the schema already states, so the baseline score of 3 is appropriate.

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 clearly states 'Navigate the subject tree' with a specific verb and resource. It explains root and sub-path behavior, distinguishing it from query/table tools, though it does not explicitly name alternatives.

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 provides how-to details (empty path lists folders, types 'l' and 't') but does not explicitly state when to use this tool versus alternatives like query_table or table_meta. Usage is implied for exploring the subject tree.

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