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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the hierarchical/subtree behavior context, which is useful beyond the annotations, but doesn't describe output shape, pagination, or recursion depth limits. The description does not contradict the annotations.

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, front-loaded with the core purpose, and the optional subtree behavior is the only additional detail. It is efficient and focused, though it could slightly expand on workspace resolution without much cost.

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, zero-required-parameter traversal tool with a full output schema, the description is adequate. The workspace_id/workspace_name optionality is captured in the schema, and the description conveys the main behavior. Missing context like default workspace fallback details or output ordering is non-critical given the schema and annotations.

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 100%, so the schema fully documents all three parameters. The description adds minimal extra meaning: it confirms folder_id can request a subtree and workspace alternatives, but this largely restates the schema. Baseline 3 is appropriate when the schema carries the parameter documentation burden.

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 a specific verb ('Get') and resource ('hierarchical folder structure for a workspace'), and distinguishes the subtree option from the full-tree behavior. It clearly differentiates from siblings like get_folder and list_folder_files by specifying the hierarchical structure rather than a single folder or flat file listing.

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 notes the optional subtree starting point and that all parameters are optional when a default workspace is configured. It clearly states the main use case but does not explicitly mention when to prefer an alternative tool like get_folder or list_folder_files, leaving some contextual comparison to the agent.

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