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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, and the description merely echoes that with "Read only; no spend." No new behavioral context is given (no pagination, filters, or account-scoping behavior), and the cryptic "Fields: soclo://tools/..." pointer is not actionable.

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-loaded, but the third sentence, "Fields: soclo://tools/soclo_ads_list_ad_studies," is opaque filler rather than useful content.

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?

With 6 parameters, a nested object, a 'confirm' flag implying spend-adjacent previews, and no output schema, the description is far too thin to let an agent call the tool confidently.

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 only 50% across 6 parameters, including a nested 'parameters' object with after/limit/fields, so the description is expected to compensate. Instead it offers nothing beyond a resource URI, leaving accountId, platform, adAccountId and the nested paging fields undocumented in prose.

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 description restates the title ("A/B tests and lift studies") without a verb, so it never says it lists or retrieves studies. The tool name carries the actual meaning; the description adds no distinguishing scope against the many other soclo_ads_list_* siblings.

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 versus alternatives such as query_ad_insights, create_ad_insights_report, or other list endpoints. Usage is only inferable from the name prefix.

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