cases_list_templates

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states 'List case templates,' with no mention of pagination, domain scoping, authentication requirements, or side effects. This is insufficient for a tool with multiple sibling operations.

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 appropriately short, but it borders on under-specification since it simply restates the tool's name. It is not verbose, but it also adds little information beyond what the name already conveys.

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?

Despite having an output schema and only two parameters, the description fails to explain key usage context such as the meaning of domain_id, the effect of max_results, or the structure of the returned templates. Given the large number of sibling template tools, this minimal description is not sufficient for reliable tool selection.

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%, and the description does not mention domain_id or max_results at all. With no parameter information in either the schema or description, an agent has no help understanding required or optional parameters.

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 uses the specific verb 'List' and clearly identifies the resource as 'case templates,' distinguishing it from sibling tools like cases_create_template and cases_get_template. However, it is terse and does not clarify scope (e.g., by domain) or the relationship to the similar-sounding template_list.

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 no guidance on when to use this tool versus alternatives such as cases_get_template or template_list. There is no mention of required context, prerequisites, or exclusion cases.

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