get_ads

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

No annotations are provided, so the description carries the full behavioral burden. "Get" weakly implies a read operation, but the description says nothing about pagination (despite a limit param), default result set size, ordering, or permissions. For a list-returning tool with zero structured behavioral coverage, this is thin.

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 short sentence, front-loaded with the action. There is no waste, though there is also almost no substance to waste.

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?

An output schema exists, so return values needn't be described, but with no annotations, 0% schema coverage, and four undocumented parameters, the description leaves the agent without enough to invoke confidently. It should at minimum explain what the filters do and how results are bounded.

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 names none of the four parameters (limit, adset_id, campaign_id, ad_account_id). It only says "optional filters," leaving the agent to infer from parameter titles alone that these are scope-narrowing filters and that limit is a page size. The description adds almost nothing beyond the 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?

"Get ads" names a specific verb and resource, so the basic action is clear. However, it offers no differentiation from siblings like get_ad_details, get_ad_previews, or get_insights, all of which also retrieve ad-related data. Beyond the bare action, an agent cannot tell from the description what scope of ads this returns versus those tools.

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?

"with optional filters" implies the tool is used to narrow a list of ads, but it names no alternatives and no when-to-use or when-not-to-use conditions. With siblings like get_ad_details competing for the same retrieval need, the absence of routing guidance is a real gap.

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