Get Migration Selective Data

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

The description adds the state requirement but largely relies on annotations (readOnlyHint=true) to convey that it's a safe read operation. It doesn't discuss edge cases or error behavior, but with annotations present, the additional context is minimal.

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 two sentences, front-loaded with the action ('Get the selective import tree for a migration') and includes a brief condition. Every sentence serves a purpose with no redundancy.

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 read operation with three parameters and no output schema, the description adequately conveys the purpose and the key state condition. It doesn't detail the tree structure but is sufficient for an agent to decide when to use it.

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 input schema covers all parameters with descriptions (100% coverage). The tool description adds no additional parameter semantics beyond what's already provided in the schema, so the baseline of 3 is appropriate.

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 retrieves the selective import tree for a migration, specifying the resource and action. It also mentions the state condition ('waiting_for_select'), which differentiates it from other migration-related tools.

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 provides a clear condition for use: only meaningful for migrations in the 'waiting_for_select' state. This gives guidance on when to invoke it, though it doesn't explicitly mention alternatives.

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