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

Annotations already state readOnlyHint=true, idempotentHint=true and destructiveHint=false, so "Read only; no spend" largely restates structured data. The wallet-safety framing adds a little product context, but nothing is said about the external platform call, result limits, or pagination for an openWorldHint tool.

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 the purpose is front-loaded, which is good, but two of the three sentences are boilerplate safety restatement and an opaque URI that reads as filler rather than information.

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 nested objects, no output schema, and half the parameters undocumented, the definition leaves too much open: what an interest result contains, which platform values are valid, and whether accountId or adAccountId is authoritative.

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 coverage is 50% and the description explains no parameters — the essential nested parameters.q query string is undocumented, as are accountId and platform. The "Fields: soclo://tools/..." pointer is a schema reference, not parameter meaning, so it does not compensate.

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?

"Search targeting interests" gives a verb and a resource, but 'interests' is never defined (interest-based ad targeting? audience interests?) and the description does nothing to separate it from the near-identical sibling soclo_ads_search_ad_targeting. An agent has the gist but not a discriminating definition.

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 when-to-use guidance at all. With siblings like soclo_ads_search_ad_targeting, soclo_ads_get_campaign_targeting, and soclo_ads_list_ad_audiences, the agent gets no signal for choosing this tool over them; "Read only; no spend" only hints that it is safe to explore.

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