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

Annotations only cover the safety profile (readOnly=false, destructive=false, openWorld=true); the description adds the traits that actually matter here: a 15-90 second latency window because OpusClip renders first, a 20-clip cap, and partial-failure semantics (failed clips don't abort the others). It doesn't discuss auth/permission requirements or whether partially imported batches can be retried safely without the idempotency key.

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 deprecation notice and the replacement tool are front-loaded in the first clause, followed by limits, latency, and return shape in descending order of decision value. Dense but no sentence is filler.

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 return-shape burden and does so: per-clip video_upload_id, caption, title, or ok:false with an error, plus what to do with each downstream. It's nearly complete for a write tool; only permission/auth expectations are unstated.

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 every parameter is already documented in structured form, including idempotency_key's retry semantics. The description's added meaning is mostly about the return fields (video_upload_id, caption, title) rather than the inputs, 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?

States a specific verb and resource with scope: imports clips of one OpusClip project into a workspace library, capped at 20 per call. It names the sibling superseding it (import_items with source opusclip), so an agent can distinguish the two 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?

Explicitly flags deprecation and names the replacement (import_items with source opusclip), which is the strongest possible routing guidance. It also gives the precondition (clip ids come from list_opusclip_clips, all from the same project) and the batch-size limit.

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