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

Goes well beyond annotations (readOnlyHint=false/openWorld/destructiveHint=false): discloses timezone conversion via store settings, the processing delay before catalog visibility, that send_email broadcasts to every member with access, the default confirmation behavior and how to disable it, and the API key/auth requirement. Rich operational context.

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?

Front-loads the core action, then layers constraints (timezone, category, processing, email, confirmation) in short, well-ordered sentences. Slightly dense with several distinct concepts but every sentence carries distinct information.

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?

Covers behavior, prerequisites, side effects, timezone handling, visibility timing, confirmation policy, and auth. For a publish tool with no output schema, nothing essential is missing.

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 already documents all four parameters (100% coverage). The description reinforces that release_at toggles between Published and Scheduled and that send_email hits every member with access, adding behavioral nuance beyond the schema's terse parameter descriptions.

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+resource (publish/schedule a video) and differentiates clearly from siblings like uscreen_update_video and uscreen_upload_video by naming the state transitions (Published vs Scheduled).

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 when to use it (publish now, or schedule by providing release_at) and names the triggering condition for each mode. Also calls out the category requirement, which determines whether the video appears in the catalog.

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