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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state the operation is a read-only list, but it says nothing about pagination via cursor/limit, account scoping via ad_account_id, or what fields a template includes. The downstream template_id note is helpful but does not cover the tool's own behavior.

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 with no filler. The primary operation is front-loaded, and the second sentence adds relevant usage context without repeating schema details.

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, the description captures the core purpose and downstream use, but with no output schema, no annotations, and undocumented parameters, the agent is left without guidance on pagination, account scoping, or expected return shape. It is minimally viable but has clear gaps.

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%, and the description adds no meaning for the three input parameters: limit, cursor, and ad_account_id. It mentions template_id, which is not an input parameter of this tool, so it fails to compensate for the schema's lack of documentation.

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 and resource: 'List saved ad templates.' It is clear about what the tool returns. However, it does not distinguish this tool from sibling adsap_google_list_ad_templates, aside from the name prefix, so it stops short of a 5.

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 gives useful downstream guidance: pass the resulting template_id to creation tools to auto-fill presets. This implies when the tool is useful, but it does not explicitly say when to prefer this over alternative list tools, nor does it mention the Google-specific sibling.

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