list_ads

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

No annotations exist, yet the description only states the basic action without disclosing behavioral traits such as read-only nature, authentication needs, or pagination. For a list operation, minimal context is provided.

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?

A single, front-loaded sentence with no unnecessary words. Every word contributes to defining the tool's action and optional filter.

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 tool with 2 optional parameters and an output schema, the description is adequate but lacks mention of required context (e.g., account_id effectively needed) or integration with sibling tools.

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 description maps account_id to 'for an ad account' and ad_group_id to filtering, adding meaning beyond the schema (which lacks descriptions). However, with 0% schema description coverage, it only provides basic mapping without details on format or constraints.

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 verb 'List' and resource 'ads' in the context of an ad account, with an optional filter by ad_group_id. It effectively distinguishes from sibling tools like list_accounts, list_ad_groups, and list_campaigns.

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 implies usage for listing ads, optionally filtered by ad_group_id, but lacks explicit guidance on when to use this instead of alternatives or prerequisites like requiring an account_id.

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