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

Annotations already declare destructive=false, openWorld=false, and notably readOnlyHint=false, so the agent knows this is non-destructive but not a pure read. The description adds the useful fact that the tool yields concrete assets (video/cover URLs, copy pack), but says nothing about whether the export renders asynchronously, consumes credits, or has latency limits — relevant given the non-read-only hint.

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 sentences, zero filler, with the resource and its outputs front-loaded before the usage trigger. Nothing redundant is repeated from the schema or annotations.

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?

Output schema and annotations cover return shape and safety, but four of five parameters — including the constrained duration and aspect_ratio that materially change the export — are undocumented in both schema and description. An agent can pick the right tool but cannot confidently parameterize it.

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% across 5 parameters, so the description must compensate and largely does not. "For a channel" only vaguely gestures at channel_preset; drop_id, team_id, duration (15–60, presumably clip length), and aspect_ratio are entirely unexplained.

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?

Specific verb ("Exports") plus resource ("drop assets") with an explicit enumeration of what is produced: video URL, cover URL, copy pack. That distinguishes it from create_drop and the regenerate_drop_* siblings, though no sibling is named outright.

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?

"Use when the user wants to download assets or prepare a drop for external publishing" gives a concrete trigger condition for selection. It stops short of exclusions or naming alternatives (e.g. when to regenerate copy instead of exporting), so it is clear context without routing rules.

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