list_template_folders

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description confirms it is a read-only listing operation. It adds value by detailing the return structure (total_items, folders array with id, name, count of templates). There is no contradiction with 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?

The description is relatively concise and well-structured with sections for purpose, usage, and returns. It could be slightly more succinct in the parameter explanation, but overall it is efficient.

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?

Given the presence of an output schema, the description adequately summarizes the return structure. It covers pagination and the main use case. The missing account parameter is a minor gap, but overall the description is complete enough for a list tool.

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 description explains the 'count' and 'offset' parameters with ranges and defaults, and hints at their pagination use. However, the schema includes a third parameter 'account' that is not mentioned in the description, and with a schema coverage of 0%, the description should compensate more thoroughly.

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 the verb 'List' and resource 'folders used to organize templates,' and specifies the use case of discovering template folder IDs before creating or organizing templates. This effectively distinguishes it from sibling tools like create_template_folder, get_template_folder, and delete_template_folder.

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 guidance on when to use the tool ('discover template folder IDs before creating or organizing templates'), and explains pagination ('Paginate with count and offset when total_items exceeds count'). However, it does not explicitly mention when not to use it or list alternative tools.

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