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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Read only; no spend' largely restates structured data. Nothing is said about what the analytics response covers, whether data is cached or real-time, or why a read-only tool's schema carries a 'confirm' parameter tied to spend/deletion approval — an oddity the description does not reconcile.

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 trailing 'Fields: soclo://tools/soclo_ads_get_campaign_analytics.' is a self-referential pointer that conveys no information to the agent and consumes a third of the text.

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?

Placeholder.

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 only 50% across 6 parameters including a nested 'parameters' object with fromDate/toDate/breakdowns, and the description explains none of them. With low coverage the description must compensate, and phrases like 'campaignId' or 'breakdowns' formats are never clarified.

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 verb and resource ('Get campaign analytics'), which is better than a tautology, but 'campaign analytics' is not distinguished from the many adjacent analytics siblings such as soclo_ads_get_ad_analytics, soclo_ads_query_ad_insights, or soclo_ads_create_ad_insights_report. An agent cannot tell from this text which analytics endpoint to pick.

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 the other analytics/insights tools in the sibling list, and no prerequisites are stated. 'Read only; no spend' is a safety hint rather than a usage rule. The agent must infer selection criteria entirely on its own.

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