youfiliate_preview_migration

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description reinforces this by stating 'Does NOT modify any data or YouTube descriptions' and explains the dry-run behavior. No contradictions.

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 concise with 5 sentences, front-loaded with the core purpose, and includes usage guidance and errors without unnecessary 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 tool's complexity (previewing a migration), the description covers purpose, safety, prerequisites, error handling, and references a sibling tool. An output schema exists, reducing need to describe return values.

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 description adds no parameter details, but the input schema provides comprehensive descriptions for all three parameters (conversion_mode, auto_geo_rules, response_format). Schema coverage is effectively high via schema, so the description's lack of parameter info is acceptable but not additive.

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's purpose: 'Preview a YouTube description migration without making changes.' It specifies the verb 'preview' and resource 'migration', and distinguishes itself from sibling tools like youfiliate_start_migration by emphasizing it is a dry-run.

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 includes when to use: 'before making changes' (implied by 'dry-run'), and prerequisites: 'Requires a connected YouTube account.' It also provides common errors and a link to a sibling tool for resolution. Lacks explicit comparison to alternatives but context is sufficient.

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