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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so safety/network profile is partly covered. The description adds the valuable async disclosure that a job handle is returned immediately and results are retrieved separately via get_job, which is a real behavioral trait beyond the annotations, but it omits credit cost, failure behavior, and result shape.

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 short sentences, front-loaded with the action and then the handoff to get_job. No filler, every clause carries 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?

With no output schema and three undocumented parameters, the description should carry more of the burden. It says nothing about what the transcript job actually returns, what mode controls, or whether lang defaults matter, leaving significant gaps for a tool an agent must invoke 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 0%: url, lang, and mode are all undocumented in the schema. The description adds nothing about any parameter – notably the meaning of mode's native/generate/auto enum and the lang selection are left completely unexplained, so an agent must guess.

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 and resource ('Start a YouTube transcript-analysis job'), which is concrete and actionable. It does not explicitly differentiate itself from job-oriented siblings like meeting_summarizer or news_analyzer, but the async-job framing is clear enough that an agent knows what it produces.

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?

Gives one piece of workflow guidance – fetch the result later with get_job – which is genuinely useful for the async pattern. It offers no when-to-use vs alternatives guidance and says nothing about the relationship to cancel_job or list_jobs, so usage context is only implied.

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