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

Annotations already declare readOnlyHint=true and destructiveHint=false, so "Read only; no spend" merely repeats structured data. Nothing is added about return shape, thumbnail generation cost, or field selection behavior.

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 the tautological opening and the opaque "Fields: soclo://tools/..." pointer consume most of the text without conveying actionable 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 tool with a nested parameter object, no output schema, and half the parameters undocumented, this definition supplies almost nothing an agent needs 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?

With six parameters (nested parameters object, creativeId required, thumbnailWidth/Height bounds, fields, requestId) and only 50% schema coverage, the description explains none of them. The "Fields: soclo://..." line is a reference URI, not parameter guidance.

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?

"Creative details" essentially restates the tool name and title without a distinct verb or scope. It does not clarify how this differs from soclo_ads_list_ad_creatives, soclo_ads_get_ad, or soclo_ads_get_ad_media.

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?

"Read only; no spend" signals safety but gives no when-to-use guidance, no prerequisites (accountId/adAccountId/creativeId), and no direction to sibling tools like list_ad_creatives for enumeration.

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