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

The annotations already include readOnlyHint: true, so the description's mention of 'List' and the GET endpoint adds no new behavioral insights. The description does not disclose additional traits like pagination limits or response format, which are not critical here but could be helpful. Since annotations carry the safety profile, a score of 3 is appropriate.

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 sentences long, front-loading the core purpose. Every word is essential: 'List the templates in the project. Filter/paginate with page, tag, name, and limit. API: GET /v2/templates.' No filler or redundancy.

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?

The tool has no output schema, but the description covers input completely. For a simple list operation with well-documented parameters, the description is adequate. It could mention that the output is a list of template objects, but the verb 'List' implies a collection. Given low complexity, a score of 4 is fair.

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 100%, so the schema already documents each parameter clearly. The description rephrases the filtering and pagination capability but adds no additional semantics (e.g., default values, order of filters). The baseline of 3 is justified because the description provides no extra meaning beyond the schema.

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 the action 'List' and the resource 'templates in the project.' It distinguishes from sibling tools like 'bannerbear_get_template' (single) and 'bannerbear_list_template_sets' (different entity). The verb and resource are specific, leaving no ambiguity.

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 clearly indicates that this tool lists templates with optional filtering and pagination. While it does not explicitly state when to avoid or use alternatives, the context is clear given the sibling tool names (e.g., get_template for a specific template). It could benefit from a note on when to use get_template instead, but the current text is sufficient for a straightforward list operation.

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