YouTube Shorts Agent Manifest

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool provides 'install, client, runtime and safety guidance', which gives some behavioral context beyond annotations but does not detail return behavior or side effects. No contradiction with annotations.

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, which is concise, but it lacks a clear structure and does not front-load the most critical information about what the tool does. It could be more informative without increasing length.

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 simple tool (2 optional params, no output schema, presence of annotations), the description is incomplete. It does not explain what the manifest contains, what the tool returns, or how the output should be used. This leaves ambiguity for an AI agent.

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?

The input schema has 0% description coverage for its two parameters ('client' and 'response_format'). The description does not mention or explain these parameters, leaving the agent to infer their meaning from names alone. This is a significant gap.

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 'Machine-readable install, client, runtime and safety guidance for agents' is somewhat vague and does not use a strong action verb. It conveys the tool provides configuration guidance but lacks specificity about its exact function, such as retrieving a manifest document. It partially distinguishes from sibling tools which perform actions like listing videos or uploading.

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 provides no guidance on when or why to use this tool versus alternatives like youtube_connection_status or youtube_privacy_audit. It does not mention any prerequisites, context, or exclusions.

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