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

Annotations already establish that this is a safe read-only operation. The description adds the useful default-scope behavior, but does not disclose whether the traversal is recursive, how results are ordered, or whether pagination applies.

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 definition is a single compact sentence with no wasted wording, and the default behavior is front-loaded in parentheses. Its terseness comes at some cost to grammatical clarity, but it is structurally efficient.

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 list tool with an output schema, the description covers the essential scope and default. It still leaves gaps around subtree depth, result ordering, and when this should be chosen over the single-budget sibling.

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 0%, so the description must carry the parameter semantics. It does clarify that the single parameter specifies a subtree and that the default is the caller's own subtree, but it does not describe the expected token identifier format or whether only direct children are included.

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 communicates that this returns budgets for tokens within a subtree, but it is phrased as a sentence fragment rather than a clear verb+resource statement. It does not explicitly distinguish the listing behavior from the sibling get_budget tool.

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?

It mentions the default scope (your own subtree) but gives no guidance on when to use this tool versus get_budget, list_token_tree, or get_usage. There are no exclusions or prerequisites.

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