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

With no annotations present, the description carries the transparency burden. It states 'REQUIRED: none' and the example 'templates_list({})' show it takes no arguments, and 'for the authenticated user' scopes the data, and the mirroring note suggests a stable contract. It does not describe return shape, but for a no-argument list operation the major behavioral risk is low.

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 compact, front-loaded with the core function, and each line ('REQUIRED: none', example) earns its place without redundancy. The Meta mirroring sentence adds useful compatibility context rather than filler.

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 tool with zero parameters and a clear 'list saved ad templates' purpose, the description is nearly complete; the output shape is not explicitly described but no output schema exists. The absence of return-format detail is a minor gap for a list operation.

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 no parameters and the description makes that explicit with 'REQUIRED: none' and the 'EXAMPLE: templates_list({})'. Since there are no parameters to explain, the description fully compensates for the missing schema detail.

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 a specific verb-resource pair, 'List saved ad templates for the authenticated user,' and the 'REQUIRED: none' plus example make the callable contract clear. It is easy to distinguish from sibling templates_create/get/update/delete.

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?

It does not say when to prefer templates_list over sibling read tools such as templates_get; the only comparative context is the Meta-compatibility note. The usage context is implied by 'List...' but no alternatives or exclusions are given.

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