migration_listBatches

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

With no annotations, description carries burden of disclosing behavioral traits. It clarifies the batch type (MIGRATE_PROCESS_INSTANCE) and active state, but omits read-only status, pagination behavior, and return structure.

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 waste. Primary purpose stated first, secondary filtering capability second. Appropriate length for a zero-parameter list operation.

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?

Adequate for a simple list operation with no input parameters. Specifies the entity type and active state. No output schema exists, but description appropriately focuses on query intent rather than return structure.

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 contains 0 parameters, establishing baseline 4 per scoring rules. Description mentions 'filter by suspended state' which implies parameter existence not reflected in schema, but adds domain context about filtering capability.

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?

Specific verb (List) + resource (migration batches) + scope (active, type MIGRATE_PROCESS_INSTANCE). Clearly distinguishes from sibling migration_listHistoricBatches by specifying 'active'.

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 filtering capability ('Optionally filter by suspended state') but does not explicitly state when to use this tool versus migration_listHistoricBatches or other batch operations.

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