get_render_preview

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

No annotations provided, so description carries full burden. It describes the tool as fetching a summary and returning a read-only preview URL, disclosing its non-destructive nature. Adds context about user confirmation step. Could mention if return is just URL or includes other data, but sufficient for a read-only preview.

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: first defines purpose, second provides workflow instructions. Every sentence is essential, no redundant words. Efficiently structured.

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?

Given simple tool (1 param, no output schema), description covers purpose, usage, and transparency. Lacks explicit mention of return value structure (e.g., object with previewUrl field), but for a preview tool this is minor. Still, it provides enough context for an AI agent to use 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% (one parameter with description). Description adds context that it fetches '当前项目的 HTML 与配音文案等摘要' but does not add new meaning 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?

Description clearly states the verb '拉取' (fetch) and resource '当前项目的 HTML 与配音文案等摘要' (current project's HTML and dubbing script summary), returning a '本机只读预览页 URL'. This distinguishes it from siblings like render_video (which renders) and get_render_status (which checks status).

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 states '渲染前必须' (must before rendering) and instructs to have user check previewUrl in browser, then pass user_confirmed_content: true to render_video only after verbal confirmation. Provides clear when-to-use and how-to-use with sibling render_video.

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