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

The annotations already declare write, destructive, and open-world behavior, and the description adds important context: the provider operation is read-only while local ads_insights rows are upserted. It does not spell out exactly what existing local data may be overwritten, but it identifies the mutated resource and clarifies the provider-side safety.

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 a single front-loaded sentence with no wasted text. The [write] marker, account selector, provider read behavior, local upsert effect, and days default are all packed efficiently.

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 an open-world, destructive sync tool with zero schema descriptions and no output schema, the definition covers the essential call behavior and side effects. It does not describe return values or error conditions, but the annotations carry the safety profile and the description covers the main operational semantics.

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%, so the description must carry parameter meaning; it identifies ads_account_id or ads_account_uuid as the account selector and explains that days defaults to the worker's sync window. It still does not clarify whether one account identifier is required or how id versus UUID should be chosen.

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: pulling one ad account's recent insight window from the provider now, with local upserts. The provider-sync framing distinguishes it from sibling insight-query tools such as ads_insights_summary or ads_insights_timeseries.

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 the tool is for refreshing data from the provider rather than querying local insights, but it does not explicitly say when to choose it over sibling insight-query tools or when not to use it. The usage context is clear enough but not fully routed.

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