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' mostly repeats structured data. The description adds no behavior beyond that: not what an unknown adId returns, not whether live=true implies higher latency/quota, not what the 'Fields: soclo://...' pointer actually refers to.

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, which is good, but the second half is a bare URI reference ('Fields: soclo://tools/soclo_ads_get_ad') that gives the agent no actionable content.

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 6-parameter tool with a nested object, no output schema and half its parameters undocumented, the description explains essentially nothing about inputs or the returned ad record. The only hint is that it is a safe read.

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% (accountId, platform, parameters, adId and live are undocumented), and the description compensates for none of it. It never mentions adId, the nested parameters object, the live flag, or how adAccountId relates to accountId.

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?

"Get ad details" restates the tool name/title word for word and adds only the 'Soclo Ads' namespace. Nothing distinguishes it from adjacent siblings such as soclo_ads_get_ad_creative, soclo_ads_get_ad_set_details, soclo_ads_get_ad_campaign_details or soclo_ads_list_ads.

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 statement of when to call this versus the many other ad-read siblings, and no prerequisites (accountId selection, whether a live fetch is needed). "Read only; no spend" describes the nature of the call, not when to choose it.

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