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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent already knows this is a non-destructive mutation. The description adds one genuinely useful trait — "Queue" signals an asynchronous enqueue rather than a direct data return — but says nothing about how the job is tracked, whether a prior queued pull is replaced, or any rate/permission constraints.

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 or redundancy. It is arguably under-specified rather than padded, but nothing in the sentence fails to earn its place.

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 mutation-ish tool with no annotation detail beyond safety hints, the definition is too thin. The output schema covers return values, but the description omits what "standard" rows include, how the async pull is monitored, and how connection_context is obtained — all things the agent needs to invoke it correctly.

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 mentions neither parameter: the lookback window (`days`, default 30) and especially the required-format `connection_context` string (mctx_v1_ + 64 hex chars) are left entirely undocumented. The description does not compensate for the coverage gap, so an agent must guess the connection token's origin.

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?

States a concrete verb+resource (queue a pull of Meta insight rows) and the qualifier "standard" implicitly contrasts with the sibling insights_pull_product_breakdowns. It is clearly not a query/read tool like insights_query_overview, though it never spells out what "standard" rows contain or how this differs from the other insights_* query 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?

No when-to-use guidance and no named alternatives, despite five sibling insights query/read/export tools that an agent must choose between. "Fresh" weakly implies fetching new data rather than reading cached results, but that is inference, not instruction, and there is no mention of prerequisites or follow-up steps.

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