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

The annotations declare readOnlyHint=false and destructiveHint=true; the description adds genuinely non-redundant context by clarifying the provider side is read-only while the local effect is an upsert into ads_audiences. That resolves the apparent tension between 'pull' (read) and the write annotations. It does not explain what 'destructive' actually means here (e.g. whether local rows missing from the provider are removed).

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 a leading [write] tag that flags the mutation class immediately. The nested parentheticals make it slightly dense to parse, but every clause carries information.

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 two-parameter sync tool with no output schema, the key facts (source, target table, side effects) are present. Missing pieces are the behavior on missing parameters and the exact scope of the destructive local write, which matter given destructiveHint=true.

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 carries the full burden; it does at least name both parameters and frames them as alternatives for identifying one account. It does not state precedence when both are supplied, the required format for the UUID, or what happens if neither is passed despite both being optional in 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?

The description names a specific verb ('Pull ... from the provider now') and resource ('audiences') scoped to a single ad account, and differentiates itself from pure-read siblings like list_ads_audiences by emphasizing a live provider fetch plus local upsert. It stops short of explicitly naming the siblings it replaces, so an agent must infer the distinction.

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 word 'now' implies an on-demand refresh, which hints at when to use this over cached list_ads_audiences, but no explicit when-to-use or when-not-to-use guidance is given. There is no mention of prerequisites such as a valid provider connection or of what to do when the account is unsynced.

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