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" largely restates structured data. The description adds nothing about pagination behavior (page/limit exist in the schema), what happens with confirm/requestId, or the shape of results for a potentially large listing.

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-loads the identification, but the trailing fragment "Fields: soclo://tools/soclo_ads_list_ads" is an opaque reference that does not convey usable information to the agent and consumes one of only three sentences.

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 six-parameter tool with a nested filter object, no output schema, and only half the parameters documented in the schema, the description is far too thin. An agent would not know what filters are supported or how results are paged or shaped without reading the raw schema.

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?

With only 50% schema description coverage and six top-level parameters including a nested filter object (status, date range, campaignId, adSetId, profileId, platformAdId), the description contributes zero parameter meaning. It never mentions the filters, the nested parameters object, or the confirm/requestId recovery contract, 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?

States a specific verb and resource ("List ads") that an agent can map to the ads collection without ambiguity about what entity is returned. It does not, however, distinguish itself from adjacent siblings such as soclo_ads_get_ad or soclo_ads_list_ad_creatives, so the sibling-differentiation bar for a 5 is not met.

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 versus the other list/get tools, no prerequisite context beyond the schema's required accountId, and no exclusions. The only usage-adjacent signal, "Read only; no spend," is a safety fact rather than routing guidance.

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