list_templates

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

No annotations are provided, so the description carries the burden of disclosing behavior. The description adds context about templates defining input/output schemas, but does not explicitly state that the operation is read-only, nor does it mention pagination, ordering, or accepted vertical values. 'List' implies a safe read operation, but more detail would improve transparency.

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 two short sentences that efficiently state the purpose and provide a brief definition of templates. No wasted words.

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 list tool with one optional parameter and no output schema, the description is reasonably complete. It explains what the tool does and what templates are, though it could mention return format or more filtering details. Overall adequate for the tool's 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?

The schema has 1 parameter ('vertical') with 0% description coverage. The description says 'by vertical' which indicates the parameter is a filter, but it does not explain what vertical refers to or what values are valid. With zero schema coverage, the description only partially compensates.

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 job templates by vertical' with a specific verb and resource, and further explains what templates are. It does not explicitly distinguish from the sibling tool 'get_template', but the list/get distinction is implied by the verb choice.

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 phrase 'by vertical' implies the tool is used to list templates filtered by vertical, but there is no explicit guidance on when to use this versus 'get_template' for retrieving a single template. No exclusions or alternative tools are mentioned.

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