processInstance_listMigratable

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

No annotations provided, so description carries full burden. It successfully discloses return value details (per-instance eligibility with call-activity blocking conditions) which is crucial behavioral context given no output schema exists. Could improve by mentioning if this is read-only or any rate limiting considerations.

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?

Extremely concise with three information-dense segments. Purpose stated immediately, followed by return value specifics, then filter capabilities. No redundant words or tautologies. Every element earns its place.

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 0 parameters and no output schema, description adequately covers the migration-specific return context (blocking conditions) and filter dimensions. Minor gap: could clarify relationship to migration planning workflow or error conditions when no migratable instances exist.

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?

Input schema has 0 parameters (empty object), establishing baseline 4. Description adds value by documenting available filters (definition key, source version, business key pattern) even though they are not formally captured in the JSON schema, suggesting query parameter interface.

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?

Description clearly states the specific action (List), resource (active process instances), and scope (eligible for migration). Effectively distinguishes from sibling processInstance_list by specifying migration eligibility criteria and call-activity blocking conditions.

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?

Implies usage context through migration-specific terminology (eligible for migration, call-activity blocking), but lacks explicit when-to-use guidance versus alternatives like processInstance_list or migration_generatePlan. No explicit exclusions or prerequisites stated.

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