list_checklist_templates

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

With no annotations, the description carries the behavioral burden. It discloses pagination semantics, page_size maximum, output_format variants, and the save_to_file side effect of writing full results to a temp file. This is strong transparency for a read-only list operation, though it does not mention authentication or rate limits.

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 with a clear opening line, a short explanatory note about templates, a compact Args section, and a Returns line. Every sentence adds useful information without unnecessary fluff.

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 list operation with no annotations, the description covers all relevant calling details: pagination, output format, file-saving behavior, and return type. Since an output schema exists, detailed return field documentation is not required. The combination of the Args documentation and example usage makes the tool safe and straightforward to invoke.

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%, but the description fully documents all four parameters: page starting at 1, page_size max 1000, output_format with enumerated valid values and default, and save_to_file behavior. It adds essential meaning that the input schema alone lacks.

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 opens with a specific verb and resource: 'List all checklist templates.' It clearly distinguishes templates from instances by explaining they are reusable checklists instantiated for organizationsholistically, and it references create_checklist for using template IDs. This removes ambiguity against sibling tools like list_checklists or get_checklist_template.

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 explains what checklist templates are used for and tells the agent to pass template IDs to create_checklist. However, it does not explicitly state when to use this tool versus alternatives like list_checklists or get_checklist_template. The usage context is implied rather than directly contrasted with siblings.

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