List Workspace Tree

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

Discloses that it loads all documents and may be slow, and mentions the inTrash flag in nodes. However, no annotations exist, so the description carries the full burden and is mostly adequate.

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 short sentences front-loading the key information with no unnecessary words.

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?

No output schema exists, and the description does not detail the return structure (e.g., node fields) beyond the inTrash flag, which may leave agents guessing.

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?

Adds the tree concept and default depth beyond the schema, but workspaceId remains undescribed. Schema coverage is 50%, and the description partially compensates.

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 it returns the full document hierarchy as a tree with depth control, distinguishing it from sibling tools like list_docs or list_children which provide flat lists.

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?

Indicates when to use (tree hierarchy) and includes a performance caveat for large workspaces, but does not explicitly contrast with alternatives like list_children.

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