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

Annotations only cover the read-only safety profile; the description adds the entire commercial behavior an agent must know: the route is paid, priced at USDC 0.01 per creator credited with a per-request minimum, settled over x402 on Celo, and an unpaid call returns the 402 payment requirements rather than data. That is exactly the kind of non-obvious operational detail annotations cannot convey.

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 first four sentences are tight and front-loaded, but the pricing model is then restated three times in near-identical form ('Priced per creator credited', 'One cent in USDC per creator credited, with a one cent minimum', 'Paid route: USDC 0.01 per creator credited, one cent minimum and 2 maximum'), which reads as repetition and the '2 maximum' phrasing is ambiguous against the earlier 'one cent minimum per request'.

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 paid, cursor-paginated feed with no output schema, the description covers returned fields, attribution semantics, pagination, and the full payment negotiation flow, which is what an agent needs to call it successfully. It is only docked for the ambiguous maximum-charge wording, which leaves the agent unsure of the per-request ceiling.

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 coverage is 100%, so the schema already documents q, sort, limit and cursor, including that limit is the cost control. The description restates the same query mechanics (?q=, ?limit=, ?sort=newest|views, nextCursor) and adds only the link between page size and per-creator pricing, so it sits at the baseline rather than adding new syntax or format meaning.

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?

Opens with a specific resource and enumerates exactly what a row contains (title, caption, hashtags, media type and length, engagement counts, thumbnail), so an agent knows this is a public post feed, not a profile or catalog. It never names the sibling tools (creator_listings, creator_profile, music_catalog) to sharpen the boundary, which keeps it just short of a 5.

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?

The description implies browsing/searching public content and states that ?q= matches title, caption, tag or creator country, and that limit/sort/cursor combine with it. It gives no explicit when-to-use-this-versus-creator_listings-or-creator_profile guidance and no exclusions, so usage must be inferred.

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