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

Annotations already declare readOnlyHint true, idempotentHint true, and destructiveHint false, covering the safety profile. The description adds meaningful behavioral detail about the output: the whole tree is returned, nested, with per-folder app counts and top-level count, and each node carries updated_at. This goes beyond the annotations and gives the agent a concrete picture of what the call returns.

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 with no wasted words. The core purpose is front-loaded, and the additional detail about counts and updated_at adds value without bloating the definition.

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 zero-parameter, read-only tool with no output schema, the description covers the essential return elements: hierarchical structure, app counts per folder, top-level count, and updated_at. It could be more explicit about the exact data shape or output format, but there is no missing information an agent would need to invoke 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?

The tool has zero parameters, so the baseline is 4. There is no schema burden for the description to compensate for. The description's focus on output content rather than any input shape 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 identifies the tool as returning the organization's entire folder tree in nested form, with counts of apps per folder and at the top level. It is distinguishable from the sibling 'ls' tool, which likely lists a single folder's contents, though it does not explicitly name that alternative.

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 implies use cases by mentioning the nested tree and the updated_at needed by 'mv', but it does not explicitly state when to use this tool versus siblings like 'ls' or 'mkdir'. There is no exclusionary guidance or alternative routing, leaving the agent to infer placement from the description.

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