list_templates

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

Annotations already establish this as a read-only operation, so the bar is lower. The description goes further by disclosing the return contents (id, name, version, dimensions) and the built-in/custom scope, which matters since there is no output schema. It does not cover pagination or auth, so not a 5.

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?

Two sentences, no filler. The result contents come first and the prerequisite workflow hint is front-loaded second.

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?

With zero parameters and no output schema, the description supplies everything an agent needs: what is listed, what fields come back, and the sequencing relative to generate_og_image.

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 tool takes no parameters (0 params), so the baseline is 4. Nothing in the description is needed to explain input, and it correctly does not attempt to.

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?

Specific verb (List) plus resource (OG image templates) with scope qualifiers (built-in and custom) and the returned fields. It is clearly distinguishable from generate_og_image, which it names.

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?

States the exact call ordering: invoke this before generate_og_image, and why (to pick a templateId). That is an explicit when-to-use with the relevant alternative named.

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