migration_listHistoricBatches

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

No annotations provided, so description carries full burden. Adds useful context about filter capabilities and persistent scoping to MIGRATE_PROCESS_INSTANCE type. However, omits pagination behavior, performance characteristics (history queries are typically expensive), and whether this is read-only (implied by 'Query' but not stated).

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?

Three efficient sentences with zero waste. Main action front-loaded in sentence 1, capabilities in sentence 2, scope constraint in sentence 3. Appropriate density for a query tool.

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 zero-parameter query tool: covers filter types and batch scope. However, lacks description of return values (no output schema present) and omits behavioral constraints like result limits or history retention boundaries.

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?

Zero parameters in schema triggers baseline 4 per rubric. Description mentions 'Filters: completion status, date range' which suggests filtering capabilities, though schema is empty. This provides conceptual context even if parameter interface is missing.

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 'Query' + resource 'historic migration batches' + source 'Operaton history log' clearly defines the action. Distinguishes from sibling 'migration_listBatches' via 'historic' designation and specific 'MIGRATE_PROCESS_INSTANCE' batch type scoping.

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 by specifying 'historic' source and available filters (completion status, date range), but does not explicitly contrast when to use this versus 'migration_listBatches' or other batch query operations. No prereqs or exclusions stated.

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