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

Annotations already declare non-readOnly, non-destructive, open-world behavior, so the safety profile is covered. The description adds that it returns run and freshness status, which is useful since there is no output schema. However, it omits that this likely starts an asynchronous run, that idempotency matters, and any rate-limit or auth details.

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 filler. It is efficient, though its brevity contributes to the parameter documentation gap.

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 7-parameter mutation/trigger tool with 0% schema coverage and no output schema, the description is far too thin. It mentions the return status but leaves the required idempotency key, date range, mode, and async-run behavior undocumented.

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% across 7 parameters, so the description must carry parameter meaning, but it only hints at account scoping. It does not explain from/to/days, the facts/full mode, workspace, or why idempotency_key is required.

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 names a specific verb ('Refresh') and resource ('Meta, Google or TikTok ad data'), with scope ('one account or all'). It is clearly a sync trigger rather than a read tool, but it does not explicitly contrast with siblings like ads_performance_get or competitor_scans_start.

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 implies usage for refreshing ad data and mentions account scope, but gives no explicit when-to-use or when-not-to-use guidance, no alternatives, and no prerequisites. The required idempotency_key and mode choice are not explained.

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