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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so 'Read only; no spend' largely restates them. 'Live' adds mild value by signalling fresh rather than cached data. It says nothing about how the fetched fields are scoped, whether missing ad sets error, or why a read tool accepts a 'confirm' parameter.

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?

Extremely short and front-loaded, which is good, but the third sentence is a bare URI fragment that conveys nothing actionable to an agent and reads as a truncated documentation link. Two of three sentences earn their place; the last is waste.

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?

Six parameters with a nested object, no output schema, and only half the parameters described leave real gaps: which identifier the tool keys on (adSetId vs. accountId vs. adAccountId), what 'fields' controls, and why 'confirm' exists on a read-only call. For a nested-parameter read tool the description does far too little.

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%, so the description must compensate, and it does not: platform, accountId, parameters.adSetId, and parameters.fields are undocumented in both places. The trailing 'Fields: soclo://tools/...' fragment is an opaque reference, not parameter meaning, and the nested parameters object is never explained.

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 specific verb and resource: 'Get live ad-set details'. The 'live' qualifier hints at current-state retrieval vs. stored data. However, it does not distinguish this from closely related siblings such as soclo_ads_list_ad_sets, soclo_ads_get_ad_campaign_details, or soclo_ads_get_ad.

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 is given. There is no mention of when to prefer this over list_ad_sets or get_ad_tree, nor any prerequisite such as needing an adSetId already resolved from a list call. The only contextual cue is 'Read only; no spend', which is a safety note rather than usage routing.

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