Get YouTube Job

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

No annotations are provided, so the description must convey behavioral traits. It discloses that download URLs are fresh and expire in 1 hour, but does not clarify behavior for non-COMPLETED states, error handling for invalid jobId, or whether the operation is read-only. Partial transparency.

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 description is a single sentence that front-loads the primary purpose and adds a critical detail. No redundancy or waste; every word serves a purpose.

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 the tool's simplicity (one parameter, no output schema), the description is complete. It tells the agent exactly what to expect: the job state and, conditionally, download URLs. No missing information for effective use.

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 100% and the parameter `jobId` has a clear description in the schema. The tool description adds value by specifying that the result includes fresh presigned URLs when COMPLETED, going beyond the schema to explain the output behavior.

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 clearly states the action ('Fetch the latest state') and the specific resource ('a YouTube job'), with a key differentiator ('fresh 1-hour presigned download URLs when COMPLETED'). It distinguishes from siblings like `get_soundcloud_job` and `list_youtube_jobs` by specifying YouTube and focusing on a single job.

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?

The description implies use when you have a job ID, but provides no explicit guidance on when to use vs. alternatives (e.g., `list_youtube_jobs` for listing, `get_job` for generic jobs) or when not to use (e.g., job not yet completed). No exclusions or context for optimal usage.

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