migration_getBatchFailures

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

No annotations provided, so description carries full disclosure burden. Compensates well by enumerating specific return fields (processInstanceId, jobId, failureType, errorMessage, stacktrace) including enum value example (EXHAUSTED_RETRIES). Implies read-only via 'Retrieve' but doesn't explicitly state safety.

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 efficient sentences with zero redundancy: first states purpose, second details return payload structure. No filler words or repetition of tool name. Well front-loaded with the verb 'Retrieve'.

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?

Lists return fields compensating for missing output schema, but fails to explain the paradox between 'one or more migration batches' in description and zero input parameters in schema—critical missing context for how batch filtering/selection is achieved. Should clarify if this returns all batch failures or uses implicit context.

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 zero parameters (empty properties object). With no parameters to document, baseline score applies. Description mentions 'one or more migration batches' but doesn't explain how batch selection occurs without input parameters, slightly detracting from perfect clarity.

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 'Retrieve' plus exact resource 'per-instance failure details for one or more migration batches' clearly defines scope. Distinguishes from siblings like migration_getBatchStatus (aggregate status) and migration_getBatchSummary (summaries) by emphasizing granular failure details.

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 debugging/introspection use case via 'failure details' and return fields (stacktrace, errorMessage), but lacks explicit when-to-use guidance versus migration_getBatchSummary or migration_getBatchStatus. No prerequisites or exclusion criteria stated.

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