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

With no annotations, the description carries the full burden and does meaningful work: it discloses the tier-based credit/paywall rules, the 'first animation free per character' unlock behavior, and that a download URL is returned. It does not say whether rendering is synchronous or a background job requiring wait_for_job (a sibling exists), nor what defaults apply to size/fps.

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?

Front-loads the core action and then groups formats into animated and still categories, which is an efficient structure. The pricing sentence is long and dense but every clause carries distinct information the agent cannot get elsewhere.

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 6-parameter export tool with no annotations and no output schema, the description covers formats, the conditional requirement, cost gating, and the return value. The remaining gaps are the meaning of `id`/`size`/`fps`/`background` and whether the call is async, which would matter for an agent orchestrating via list_jobs/wait_for_job.

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 0%, so the description must compensate, and it does so well for `format` (explaining lottie as true vector, sticker as die-cut, logo as vector badge) and for `animation` (a name/id or preset, required for sprite). However `id`, `size` (units?), `fps`, and `background` get no explanation, leaving half the parameters to be guessed from types and ranges.

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 verb and resource ('Render a mascot to a file') and immediately enumerates the full set of output formats, so the agent knows exactly what the tool produces. The 'mascot' object also naturally separates it from the sibling export_clip without opening either schema.

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?

Gives concrete selection guidance among formats (animated vs still, and that 'sprite' requires an `animation` value) plus the credit cost implications that would steer a choice. It stops short of naming alternatives such as export_clip or get_mascot, so the when-not guidance is implicit.

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