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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'GET /ugc' adds nothing beyond what the annotations say. No mention of pagination behavior, rate limits, or result size despite a per_page parameter, so the description contributes almost no behavioral context.

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?

Two short front-loaded fragments with no padding; the resource is stated before the filter list. The trailing 'GET /ugc' is redundant with the annotations, a minor waste of space.

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 read-only list tool with a fully documented schema and annotations covering the safety profile, the essentials are present. However, it says nothing about return shape or pagination (no page cursor is exposed, only per_page), leaving the agent to guess how to page through UGC results.

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 100%, so all five parameters are already documented, including the semicolon separator convention and the 1-100 per_page range. The description only restates the filter dimensions at a high level, adding no syntax or default-value detail, which is the expected baseline 3.

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 resource (customer photos/videos UGC) and the filter dimensions it supports, which distinguishes it from text-review siblings like reviewsio_list_reviews. It never names an alternative sibling explicitly, so it stops short of a 5, but the resource is unambiguous.

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?

Lists what you can filter by ('SKU, tag, category or videos only'), which implies the use case, but gives no explicit when-to-use guidance, no prerequisites, and no statement about when to prefer the review-listing siblings instead.

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