list_template_folders

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=false. Description adds 'Authenticated via API key. Max 10 concurrent requests. Read-only, safe to retry,' which provides auth method, concurrency limit, and retry safety that go beyond annotations. No contradictions.

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 well-structured: first sentence states purpose, then usage, then a line on auth/limits, then Args section, then Returns section. Every sentence adds value, no fluff. Front-loaded with the most important info.

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 listing tool with pagination and optional account, the description covers purpose, usage, pagination mechanics, auth, rate limits, parameter details, and return format. Output schema is described. Complete for its complexity.

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?

Despite 0% schema description coverage, the description explains all three parameters in detail: count (1-1000, default 10), offset (pagination), account (optional, with example 'marketing' and reference to list_accounts). Also describes return format with total_items and folders array, adding value.

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 'List folders used to organize templates' and adds context 'Use to discover template folder IDs before creating or organizing templates.' This distinguishes it from sibling tools like list_templates (which lists templates) and create_template_folder (which creates folders).

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?

Explicitly says when to use: 'Use to discover template folder IDs before creating or organizing templates.' Provides pagination guidance with count and offset. Mentions optional account and refers to list_accounts. However, does not explicitly state when not to use or contrast with alternatives, but it's clear enough for a simple list tool.

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