folder_get

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

No annotations are provided, so the description carries the full burden. It states 'Safe to call repeatedly; no side effects,' which is good. However, it does not disclose behavior for invalid IDs or potential errors, and could mention whether the folder must exist.

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 plus an example, front-loaded with purpose. Every sentence adds value—usage guidance, return fields, safety, and a concrete example. 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?

For a simple get-by-ID tool with no output schema, the description covers purpose, usage, parameters, return fields, and safety. It is complete enough for an AI agent to select and invoke correctly, especially given the rich context from sibling tools.

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 coverage is 100% (both params described). The description adds significant meaning: for `id`, it explains how to obtain it (`Get from folder_list`) and stability; for `verbose`, it explains the effect on output shape and references documentation. This goes well beyond the schema alone.

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 'Fetch a single folder by its persistent ID'—a specific verb and resource. It explicitly distinguishes itself from the sibling tool `folder_list` by warning 'Do not use to list multiple folders; prefer folder_list instead.'

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 provides explicit when-to-use ('Fetch a single folder') and when-not-to-use ('Do not use to list multiple folders') guidance, and names the alternative (`folder_list`). It also adds context that the tool includes counts and is safe to call repeatedly.

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