Get Migration Selective Data

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

The description adds the state constraint and defines the returned data as a tree/list of content items, which goes beyond the readOnlyHint and openWorldHint annotations. However, like many read-only tools, it does not describe return format, pagination, or filtering behavior in depth.

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 concise sentences with no wasted words. The core resource is front-loaded, and the critical state constraint is stated immediately after the definition.

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 simple three-parameter read-only tool, the description plus schema is nearly complete. It explains what the tool returns and when it applies, though with no output schema it could add slightly more about the response shape.

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 already provides 100% description coverage for all three parameters, including the optional 'type' filter. The description adds no further parameter-specific meaning, so the baseline of 3 applies.

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 a specific verb and resource — 'Get the selective import tree for a migration' — and clarifies what that means ('the list of content items available to selectively import'). This clearly distinguishes it from generic migration tools like get_content_migration and aligns with the tool's name.

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 an explicit usage condition: 'Only meaningful for migrations in the "waiting_for_select" state.' This tells an agent when to use it and implicitly when not to, though it does not name an alternative tool for other states.

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