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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so 'Read only; no spend' largely repeats structured data. The description adds no information about return format, URL expiration, authentication needs, or error behavior, and the 'Fields: soclo://tools/soclo_ads_get_ad_media' line is confusing rather than informative.

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?

The description is short and front-loads the purpose, but the second sentence ('Fields: soclo://tools/soclo_ads_get_ad_media') does not earn its place and may confuse 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 six parameters (including a nested object) and no output schema, the description is insufficient. It neither explains how to supply the required adId/accountId nor describes what the returned media URLs look like or whether they expire.

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%, and the description provides no parameter details at all—not even for the required nested adId. It does not compensate for undocumented parameters such as accountId, platform, or the parameters object.

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 states a specific resource ('Direct video and image URLs for an ad'), which is clear enough to distinguish it from generic ad-listing tools like list_ad_images or list_ad_videos. However, it uses a noun phrase rather than a verb and does not explicitly name the sibling alternatives it replaces.

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 versus soclo_ads_get_ad, soclo_ads_get_ad_creative, or soclo_ads_list_ad_images. The only contextual statement is 'Read only; no spend,' which is a safety note rather than a usage condition.

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