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

Discloses tier-specific behavior (sandbox vs real upload) and OAuth requirement. However, does not explain asynchronous nature (queues), error handling, or side effects of the publish parameter. Without annotations, more detail is needed.

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 sentences, front-loaded with main action. No superfluous information, well-structured and efficient.

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 core action and tier differences but lacks parameter descriptions, output format, and asynchronous behavior. Adequate for a simple tool but incomplete given no output schema or annotations.

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 coverage is 0%, yet description adds no explanation of parameters. 'tenantVideoId' and 'publish' are not described; agent must infer meaning from context. Very little value beyond parameter names.

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 'Upload a generated draft to YouTube' with specific verb and resource. It distinguishes from sibling tools like youtube_generate_video by specifying the upload action and tier differences.

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?

Provides guidance on when to use based on tier (free vs Pro/Studio) and mentions authentication requirement. Implicitly indicates it's for uploading drafts after generation, but lacks explicit alternatives or when-not-to-use conditions.

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