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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the description only needs to add operational context. It does so usefully, disclosing that counts are inclusive of subfolders, that results form a tree, and that the output feeds the `folder` parameter of other tools. Return formatting or pagination for large accounts is not discussed.

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?

Three sentences, each carrying distinct information: what is returned, when to call it, and how its output is consumed by siblings. No restatement of the title and no 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?

With no parameters, no output schema and an empty input object, the description carries the full burden of explaining what comes back — and it describes the tree, per-folder fields and account totals in enough detail to act on. Nothing essential is missing for a zero-argument read.

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 takes no parameters, so the baseline is 4; there is nothing the description could add on the input side. It does usefully document the semantics of the outputs that serve as inputs elsewhere.

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 names the resource (folders on the user's TransformPipe account) and the shape of the result as a tree, and enumerates the returned fields (id, path, document count including subfolders, sharing state) plus account totals. This is concrete enough to distinguish it from tp_list_documents and tp_usage, which cover different resources.

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 gives explicit triggers — user asks about folders or document counts, or another tool needs a folder id/path — and states the interoperability contract that returned ids/paths are accepted as `folder` by other tools. It lacks an explicit when-not-to-use or named sibling alternative, so it stops short of a 5.

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