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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds important behavioral context about response-size caps and potential refusal for large organizations, which goes beyond the annotations. It also notes that `ownerTeamId` may 404 when the team has no readable Process Landscape, a useful edge case.

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 a single sentence that front-loads the core purpose, then succinctly adds usage guidance for size limits. Every clause adds value, with no redundancy or filler.

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 read-only tree-fetch tool with no output schema, the description covers the essential decision points (scoping parameters and response-size risk). It lacks detail on the exact structure of the returned tree, but that is likely acceptable given the simple read-only nature. The 404 behavior for `ownerTeamId` is a useful addition.

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 only 33%, with only `ownerTeamId` having a schema description. The tool description compensates by explaining the purpose of `rootId` and `ownerTeamId` in narrowing results, adding semantic meaning beyond the schema. For `orgId`, the schema provides its UUID format, which 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?

The description clearly states the tool fetches the organization's process tree, optionally narrowed by `rootId` or `ownerTeamId`. The verb 'Fetch' and resource 'process tree' are specific, and the description distinguishes it from related siblings like `getClarityProcessLandscape` by focusing on the tree structure and scoping.

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 explicitly advises when to use `rootId` (for one subtree) or `ownerTeamId` (for one team's processes) to avoid response-size refusals. It also warns against fetching the whole organization tree when too large, providing clear context for when to narrow.

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