youfiliate_disconnect_youtube

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

Discloses that it removes OAuth tokens and does not modify YouTube data, adding context beyond annotations. Annotations include destructiveHint=true, and the description confirms this without contradiction.

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?

Well-structured with clear sections (action, important note, common errors). Every sentence adds value, and the content is appropriately concise for a simple tool.

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 one parameter and simple functionality, the description covers behavior, safety, errors, and output, making it complete. An output schema exists but isn't shown here.

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 only parameter (confirm) is thoroughly explained, including its necessity and the requirement for user confirmation. The description adds meaningful context beyond the schema's parameter description.

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 'Disconnect your YouTube account from Youfiliate' with a specific verb and resource. It distinguishes from sibling tools like connect_youtube and check_link_health.

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?

Explicitly states the need for user confirmation and provides common errors. While it doesn't mention alternative tools, the purpose is clear enough for correct selection.

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