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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds "Read only; no spend," which usefully confirms there is no financial side effect, but otherwise repeats the annotation profile and says nothing about rate limits, data freshness, or permissions.

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 short and front-loads "Get ad analytics," but it wastes space on the redundant "Soclo Ads:" prefix and an unexplained URI that the agent cannot act on. It is concise to the point of under-specification rather than efficient communication.

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?

This is a 6-parameter analytics tool with a nested parameters object and no output schema, yet the description does not explain what metrics or breakdowns are returned, how dates are handled, or what the adId scope means. The annotations cover safety, but the description leaves too many functional questions unanswered.

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?

The description provides no parameter meaning; "Fields: soclo://tools/soclo_ads_get_ad_analytics" is a reference pointer rather than inline semantics. With only 50% schema description coverage and nested parameters like adId, fromDate, toDate, and breakdowns undocumented in the description, the agent gets no help beyond the partially described 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 states a verb and resource ("Get ad analytics"), but it is essentially a restatement of the title and does not specify which analytics, for which entity, or over what range. Many sibling tools exist for analytics (e.g. soclo_ads_get_campaign_analytics, soclo_ads_query_ad_insights, soclo_ads_get_ad_insights_report), and the description gives no way to distinguish this tool from them.

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 such as soclo_ads_get_campaign_analytics or soclo_ads_query_ad_insights. "Read only; no spend" is a safety note, not a usage condition, and no prerequisites or exclusions are stated.

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