get_ads

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

Description indicates a read-only list operation, but no annotations provided. Does not mention side effects, rate limits, or pagination behavior beyond the limit parameter. Adequate but minimal.

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?

Starts with a clear one-liner, then bulleted parameter list. No redundant information, each sentence adds value. Efficient and well-structured.

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?

Lacks return value description (e.g., fields of ad objects) or pagination details beyond limit. Despite good parameter coverage, the absence of output schema and explanation of results reduces completeness.

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?

With 0% schema description coverage, the description compensates fully by providing explanations, examples (e.g., 'act_123456789'), and defaults (limit=50). Adds significant meaning beyond the bare 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?

Clearly states the tool lists ads, with specific scope (account, campaign, or ad set). Distinguishes from siblings like get_ad_details (single ad) or get_ad_creatives (creatives).

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?

Implicitly useful for listing ads with filters, but no explicit guidance on when to use this versus alternatives like get_ad_details or get_ad_creatives. Lacks exclusion criteria.

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