get_tree_summary

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

With no annotations, the description states that the tool returns a high-level structure with child counts, indicating it is a read operation. However, it does not disclose potential performance implications for deep hierarchies or error handling for invalid paths.

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 sentences clearly convey purpose and output characteristics. No unnecessary information.

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?

Given no output schema, the description could more explicitly describe the return format (e.g., list of nodes with counts or nested structure). However, the phrase 'hierarchical summary with child counts' gives a reasonable mental model. Missing details like error cases or limits.

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 have descriptions in schema (100% coverage), and the description does not add additional semantic information beyond what is in the schema. The default value for depth is noted only in schema but not in description, but schema is sufficient.

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?

Description uses specific verb 'Get' and resource 'hierarchical summary with child counts', clearly indicating the tool's output for drill-down navigation. It distinguishes from siblings like get_document_summary and get_node_details by emphasizing 'high-level structure without full node details'.

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?

Description implies usage for drill-down navigation but does not explicitly state when to use this tool over siblings like get_document_summary or list_pages. No exclusions or when-not-to-use mentioned.

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