youfiliate_list_migrations

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description reinforces that it does not modify data and returns a paginated list. It adds context about pagination but does not disclose additional behavioral traits like rate limits or the structure of the returned data. With strong annotations, this is adequate but not exceptional.

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 two sentences, front-loading the purpose. Every sentence adds value: it states what the tool does, that it returns a paginated list, and that it does not modify data. 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?

The description provides the core purpose and safety assurance, but lacks details about the return format (though there is an output schema), pagination behavior details, filtering options, and differentiation from sibling tools. For a simple listing tool, it is minimally complete but could be improved with more context.

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 description coverage is reported as 0%, meaning the schema does not describe its parameters (though the provided schema has descriptions for limit and offset, but the signal indicates 0% coverage). The description only mentions 'with pagination', which vaguely hints at pagination but does not explain the limit, offset, or response_format parameters. The description fails to compensate for the lack of schema descriptions.

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 it lists migrations with pagination and returns a paginated list. It uses a specific verb 'List' and resource 'migrations'. However, it does not explicitly differentiate from the sibling tool 'youfiliate_get_migration_status', which might get a single migration's status.

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 mentions 'Does NOT modify any data', indicating safe usage. However, it does not provide when-to-use guidance versus alternatives like 'youfiliate_get_migration_status' or any prerequisites (e.g., needing a YouTube connection). The usage context is implied but not explicit.

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