list_migrations

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description doesn't need to restate that. It adds useful context about what migrations orchestrate, but it does not disclose behaviors such as pagination, ordering, or response size; still, the bar is lower because annotations cover the main risk.

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?

Two sentences with no filler. The primary action is front-loaded, and the domain context is provided in a compact second sentence that helps with tool selection without bloating the description.

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 read-only listing tool with one optional parameter and an output schema, the description is complete. It explains what a migration is, what the tool does, and that filtering is possible—nothing critical is missing for an agent to invoke it correctly.

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 describes the single parameter fully with an enumerated list, so the description need not add much. Mentioning 'Optionally filter by status' matches the schema but doesn't add new meaning beyond what the structured definition already provides.

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 opens with a specific verb and resource ('List all migrations'), immediately distinguishing it from single-migration tools like get_migration. It also clarifies the domain meaning of a migration, which helps an agent understand the tool's scope before calling it.

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 gives clear context that this is the general listing tool, with an optional status filter. It doesn't explicitly name alternatives or exclusions, but the self-contained nature of a list operation makes the primary use case unambiguous.

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