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, though 'no spend' mildly reassures against billing side effects. Nothing is said about pagination, result limits, filter behavior, or what the reference 'soclo://tools/soclo_ads_list_ad_sets' resolves 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?

The description is short and front-loads the operation, which is good, but the trailing 'Fields: soclo://tools/soclo_ads_list_ad_sets' is a cryptic pointer that consumes space without conveying actionable meaning. Brevity here reflects under-specification rather than disciplined editing.

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 tool with a required account identifier plus an undocumented nested parameter object, no output schema, and dozens of closely named sibling list tools, the description leaves the agent without enough to call it correctly or know what it returns. The annotations cover the safety profile but not the operational detail this tool needs.

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% with 6 parameters including a nested 'parameters' object whose live/adSetId/campaignId sub-fields are undocumented in both schema and description. The description supplies zero parameter guidance (no accountId vs adAccountId distinction, no platform values), so it fails to compensate for the coverage gap.

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 phrase 'List ad sets' is a clear verb+resource but restates the title verbatim, adding no differentiation from the many siblings such as soclo_ads_get_ad_set_details (single ad set), soclo_ads_list_ads, or soclo_ads_list_ad_campaigns. An agent can tell it is a list operation on ad sets, but nothing distinguishes its scope from adjacent read tools.

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 use this tool versus soclo_ads_list_ad_campaigns, soclo_ads_get_ad_set_details, or the various filtered list tools. 'Read only; no spend' signals safety rather than a selection condition, so the agent must infer usage from the name alone.

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