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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so "Read only; no spend" is largely redundant with structured data. The only added context is that the call incurs no spend, plus an unexplained "Fields: soclo://tools/..." pointer that gives no actual behavioral detail (rate limits, pagination, latency).

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?

It is short and front-loaded, but the cryptic "Fields: soclo://tools/soclo_ads_query_ad_insights" fragment consumes space without conveying meaning. Brevity here reflects under-specification rather than efficient writing.

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?

A tool with a nested 20+ field parameter object, mixed platform conventions (Meta-style vs Google-style fields), and no output schema demands far more description than three short clauses. Nothing tells the agent how to shape a valid query or interpret the response.

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 50% and the description adds nothing about the six top-level parameters or the 20+ nested `parameters` object fields (datePreset vs fromDate/toDate, pageToken vs after, level vs dataLevel, confirm/requestId semantics). The only nod to parameters is a dangling resource URI that an agent cannot resolve from the text alone.

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?

"Flexible live insights query" essentially restates the tool name and title, adding only the adjectives "flexible" and "live." It never says what an insights query returns or how it differs from the many adjacent analytics siblings (get_ad_analytics, get_ad_insights_report, create_ad_insights_report, get_campaign_analytics).

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. With dozens of overlapping ads-analytics tools in the sibling list, the agent is left to guess entirely.

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