youfiliate_rollback_migration

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

Disclosures beyond annotations: modifies YouTube descriptions, asynchronous operation, requires confirmation. Annotations provide destructiveHint=true, but description adds critical context about user confirmation and asynchronicity.

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?

Description is concise and well-structured: main action first, then important warnings, then common errors. No unnecessary sentences.

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?

For a destructive tool with 2 parameters and an output schema, the description covers purpose, usage, prerequisites, and error conditions comprehensively. The output schema likely covers return values, so no need to duplicate.

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?

Despite schema description coverage of 0% (though schema actually includes descriptions), the tool description thoroughly explains the confirm parameter and its importance. It reiterates the id parameter's purpose (Migration UUID) and provides usage guidance.

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?

Description clearly states 'Roll back a completed migration, restoring original YouTube descriptions.' This provides a specific verb and resource, and distinguishes from sibling tools like youfiliate_start_migration.

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?

Description explicitly instructs to confirm with the user before executing and lists common errors including the need for confirm=True. It also mentions the prerequisite of a connected YouTube account. However, it does not explicitly state when not to use this tool versus alternatives.

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