get_all_folders

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates a read operation with account-level scope, but it is silent on pagination, ordering, hierarchy behavior, access requirements, or whether the result includes system-generated folders.

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 clear sentence with no redundant wording. It front-loads the action, resource, and scope, and every word earns its place.

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 tool with a single required parameter and an output schema, the description is minimal but functional. However, the lack of usage guidance, parameter clarification, and behavioral context like pagination makes it incomplete for an agent choosing between many sibling tools, especially with no annotations to fill the gap.

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 0%, so the description needs to explain the account_id parameter. It only says 'in account', which weakly implies account_id is the account scope, but it does not clarify what values are valid, where to find the id, or whether the id refers to a user account or organization account.

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 states a specific verb ('Get'), resource ('folders'), and scope ('in account'). This clearly distinguishes the tool from sibling tools like create_folder, rename_folder, and get_all_labels, although 'account' is slightly ambiguous without defining what an account is.

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?

There is no guidance on when to use this tool versus alternatives like get_folder_details or get_all_labels. The description implies a list-all use case, but it does not explicitly state exclusions, prerequisites, or scenarios where another folder tool would be more appropriate.

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