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

Annotations declare readOnlyHint=false and idempotentHint=false, and the description corroborates this by describing a write that produces a new asset added to the library. It adds genuinely useful behavioral context beyond annotations: render time ('up to a couple of minutes') and a 24h-valid download link. It does not explicitly address auth requirements or repeat-call behavior.

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?

It is a single dense paragraph but front-loads the core action and then adds routing info in logical order. Nearly every sentence carries actionable content, though the rendering/format sentence is somewhat long.

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-value burden and does so adequately: it names the returned asset id and the 24h download link. Render duration is disclosed. Minor gaps remain around the exact return shape and failure behavior.

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 including defaults and enums is already documented in the schema. The description restates a couple of these (default asset, on-screen text fallback) but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb+resource ('Make a basic edit of an analyzed post and deliver it') and then enumerates exactly what the edit does: overlay text, replace sound, render a 1080x1920 MP4. It is clearly distinguishable from siblings like assign_edit or dispatch_video.

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?

It explicitly routes the agent: post id comes from list_analyzed_posts, assets from get_post_analysis or search_assets, and the finished reel is sent to a poster via assign_edit. When-to-use and the alternative workflow are both stated without inference.

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