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

With annotations covering the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description adds real operational context: input constraints, the returned key, and the downstream dependency chain. It does not clarify idempotency behavior (whether re-uploading the same URL duplicates media) or any auth requirements. Minor tension: it fetches arbitrary public URLs while annotations declare openWorldHint=false, though this reads more as an annotation imprecision than a description error.

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?

Three tight sentences, front-loaded with the core action and return value, then workflow placement, then network-specific requirement. Every clause carries information; none is redundant.

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?

No output schema exists, and the description supplies the one return value an agent needs (`key`). Combined with the explicit placement in the post workflow and the media-vs-URL distinction, an agent has everything required to call it correctly.

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 both `url` and `alt` are already fully documented structurally. The description restates the format/size constraints already present in the schema and says nothing about `alt` semantics, so it adds little beyond the baseline.

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 (copies) and resource (public image/video into Broadcast), names the accepted formats and size caps, and explicitly identifies the returned artifact (`key`). It is immediately distinguishable from sibling write tools like schedule_post and update_post.

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?

Explicit ordering instruction ('Call it before schedule_post or update_post whenever the post has media'), an exclusion ('a plain URL is not accepted there'), and a required-case note for Instagram/TikTok. This is a model example of when-to-use and when-not-to-use guidance.

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