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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the pagination behavior and confirms no data modification, but this mostly reinforces annotations. There is no contradiction, but limited additional behavioral context beyond what annotations provide.

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 and front-loaded. The first sentence states the action and resource, and the second adds a safety clarification. Every sentence earns its place, with no wasted words.

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 annotations (read-only, idempotent) and the existence of an output schema, the description is fairly complete. It clearly states the paginated nature and non-destructive behavior. The only minor gap is no mention of default ordering or field details, but the output schema covers 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 schema provides full descriptions for all parameters (limit, offset, response_format), so the baseline is 3. The tool description mentions pagination generally but does not explain parameter syntax or add meaning beyond the schema. Schema coverage is effectively high, so description compensation is not required.

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 uses the specific verb 'List' and clearly identifies the resource as 'YouTube description migrations.' It also mentions pagination, which distinguishes it from migration status or preview tools. This is unambiguous and differentiates from sibling tools like get_migration_status and preview_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?

The description implies usage for listing migrations without modification, but it does not explicitly state when to use this tool over alternatives. No exclusions or alternative tool references are provided. The context is clear but not fully explicit.

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