get_root_folder

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does clarify that this is a read-oriented operation returning a root folder plus unmapped folders, which is useful. However, it does not mention behavior for invalid ids, error cases, or whether any additional data is included beyond what is stated.

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, efficient sentence that front-loads the core purpose and immediately adds the most important behavioral detail. There is no redundant or filler content.

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 simple one-parameter getter, the description is largely complete: it names the resource, the singular scope, and a key part of the returned data. Since there is no output schema, explaining that unmapped folders are included adds value, though the exact shape of the root folder response is not detailed.

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 only parameter, id, is already fully described in the schema as 'Root folder id,' giving 100% schema description coverage. The description adds no additional parameter-level meaning, but the schema alone is sufficient for this simple case.

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?

States a specific verb and resource: 'Get one root folder' — clearly singular, differentiating it from list_root_folders, add_root_folder, and delete_root_folder. It also adds the key distinguishing detail that the result includes the full list of unmapped folders, which is meaningful and specific.

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 makes the tool's intended use clear: retrieve one root folder by id along with its unmapped folders. It does not explicitly name sibling alternatives or state when not to use this tool, but the singular nature of the description gives enough context to guide selection.

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