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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so 'Read only; no spend' mostly repeats structured data. The one useful addition ('no spend') is minor; nothing explains rate limits, return shape, or the effect of the confirm/requestId fields.

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 but badly under-specified for a six-parameter tool. The trailing 'Fields: soclo://tools/...' reference is opaque indirection that occupies space without conveying meaning to an agent.

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 nested parameters, an object of enums (geoType, dimension), no output schema, and only 50% schema coverage, the description should carry far more context than it does. As written it leaves the agent without the targeting-dimension semantics needed to call it correctly.

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 mentions no parameters at all, and schema description coverage is only 50% (q, limit, geoType, dimension, countryCode are undocumented). The 'Fields: soclo://...' line points to an external reference rather than explaining any of the six parameters, leaving the enum-heavy targeting inputs opaque.

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 verb+resource ('search targeting options') but 'targeting options' is vague and essentially restates the title 'Search targeting options'. It does not distinguish this tool from the very similar sibling soclo_ads_search_ad_interests, so an agent cannot easily tell which to pick without opening schemas.

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 vs alternatives such as soclo_ads_search_ad_interests, and no stated preconditions. 'Read only; no spend' is a minor signal but not usage direction.

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