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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description's one genuine contribution is the 500-node cap, which hints at result size limits, but it does not say whether exceeding it truncates, errors, or paginates — a material behavior for a tree read.

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?

It is a single front-loaded clause with zero filler, which suits a low-complexity read tool. The terseness is a completeness problem rather than a verbosity one, so it is penalized elsewhere rather than here.

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?

An output schema exists, so return shape need not be described, but three parameters at 0% schema coverage and an unexplained depth/rollup semantic leave too much to inference. For a hierarchical traversal tool with a hard node ceiling, the definition does not give enough to call it correctly.

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 description coverage is 0% across three parameters, so the description is the only source of semantics beyond names and defaults. It contributes the node cap and the notion of children summaries (which loosely relates to the include enum), but depth, its 1–4 range and default of 2, and the summary/rollup distinction go entirely unexplained.

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 fragment names the resource (task tree) and its scope ('under a task', 'at most 500 nodes'), so an agent can infer this is a read of a task's hierarchy. But it is a noun phrase with no verb, and it largely restates the name get_task_tree; the only real additions over the title are the node cap and 'with children summaries'.

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?

There is no when-to-use guidance at all, despite many plausible alternatives in the sibling list (list_tasks, get_tenant_tree, get_lineage, update_task). Nothing tells the agent whether this is the right tool for browsing a hierarchy versus listing tasks flatly, and there are no stated prerequisites.

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