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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's real contribution is return-shape context: every Rate carries a stable id, a price expressed under one of three visibility modes (full, from_price, request_only), inclusions, and self-reported audience. That visibility-mode detail is genuinely useful and not derivable from the schema. It stops short of saying what happens when a creator has no rate card.

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?

One dense, front-loaded sentence with no filler; the resource is named first and the contents follow. It is a noun-phrase fragment rather than a sentence, which slightly weakens readability but wastes nothing.

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 no output schema, the description carries the burden of describing returns and does so well: ids, price visibility modes, inclusions, audience. Annotations cover the safety profile. The main missing piece is the edge case of a creator with no published rate card, which an agent would want to know before calling.

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?

Only one parameter, and the schema documents it at 100% coverage ('The creator's Piku handle, like nia'). The description adds only the possessive framing ('a creator's Rate Card'), which does not extend the schema's meaning, so the baseline 3 applies.

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 names the resource precisely (a creator's Rate Card and media kit) and enumerates its contents: rated items with stable ids, price visibility modes, inclusions, and audience. It is clearly distinguishable from invoice/deal/page siblings, though it never contrasts with search_creators, which also takes a creator handle.

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?

Usage is implied: given a creator handle, this returns their pricing and audience data. There is no explicit when-to-use statement, no mention of prerequisites (does the creator need a published rate card?), and no routing against siblings like search_creators or get_deal.

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