mc_listTemplateFolders

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

With no annotations, the description must disclose behavioral traits. It only says 'List', implying a read operation, but lacks details on pagination behavior (though parameters suggest it), ordering, or any side effects. The agent needs more information to understand what happens when the tool is invoked.

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 extremely concise (two words), front-loading the core action. While it lacks detail, it has no superfluous content. It could be improved with a touch more context (e.g., 'List all template folders with pagination') without sacrificing conciseness.

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 two parameters with good schema but no output schema, the description is incomplete. It does not explain what the output looks like, how pagination works, or the default behavior. Sibling tools like mc_listFileFolders likely have similar descriptions, but this one lacks necessary context for an agent to use it effectively.

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%, with both parameters (count and offset) described in JSON schema. The description adds no additional meaning beyond the schema, so the baseline score of 3 applies. No extra context is provided.

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 'List template folders' clearly states a verb ('List') and a resource ('template folders'). It is not a tautology and distinguishes from sibling tools like mc_getTemplateFolder (which gets a specific folder) and mc_listTemplates (which lists templates, not folders). However, it could be more precise by specifying scope (e.g., 'all' or 'paginated').

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like mc_listFileFolders or mc_getTemplateFolder. There is no context on prerequisites, exclusive use, or when to choose another tool.

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