list_folders

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one useful trait beyond that ('Shared folders are read-only'), but says nothing about pagination behavior despite the limit/cursor parameters, so it only partially enriches the annotation baseline.

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 clauses, front-loaded with the primary action and no filler. It is efficient, though the second sentence about shared folders feels appended rather than integrated.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. The only real gap is pagination/cursor behavior, which is minor for a simple read-only list tool whose required parameter and parent-scope mode are stated.

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 carries the full burden, yet it only implicitly explains parentFolderId ('children of one folder') and accountId scope. The limit and cursor parameters are undocumented in both schema and description, leaving pagination semantics entirely unclear.

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 gives a specific verb and resource ('List folders in an account') plus a dual mode ('optionally list children of one folder'), making the scope clear. It is distinguishable from note-oriented and folder-mutation siblings by resource, though it never names an alternative tool explicitly.

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 clause 'optionally list children of one folder' implies when parentFolderId should be supplied, so usage is inferable. However, there is no explicit when-to-use versus siblings like create_folder/delete_folder, and no statement of when not to use it.

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