youtube_connection_statusVerify YouTube Shorts upload readiness by checking dry-run mode, OAuth authentication, and live upload availability without revealing tokens.
Check dry-run mode, OAuth readiness and live upload readiness without exposing tokens.
| Name | Required | Description | Default |
|---|---|---|---|
| response_format | No | json |
Changes observed during successful MCP inspections.
v0.1.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent. The description adds value by specifying the exact readiness aspects checked (dry-run, OAuth, live upload) and explicitly states tokens are not exposed, providing useful behavioral context beyond 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, front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose and key safety detail.
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 simplicity of the tool (one optional parameter, no output schema, clear annotations), the description provides all necessary context: what is checked, that tokens are not exposed, and the read-only nature is reinforced.
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% and the description does not mention the 'response_format' parameter or its enum values. Since the parameter is simple, the oversight is minor but still fails to add meaning beyond the schema.
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 tool checks dry-run mode, OAuth readiness, and live upload readiness, which is a specific verb and resource. It distinguishes from siblings like youtube_oauth_authorize_url and youtube_upload_short by focusing on status checks.
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 usage when needing readiness status, but lacks explicit guidance on when to use vs alternatives or exclusions. It does not mention when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.