migration_getBatchSummary

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

No annotations provided, so description carries full disclosure burden. Adds useful context by listing returned fields and 'post-migration' timing, but omits mutation safety confirmation (implied by 'get' but not stated), error behaviors, or prerequisites. Does not contradict implied read-only nature.

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 efficiently structured sentences. First sentence front-loads function and data points; second provides usage context. Zero filler or redundancy—every word 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?

Compensates well for missing output schema by enumerating aggregate fields in description. Covers timing (post-migration) and purpose (sign-off). Lacking only error-handling guidance and auth/permission notes for full completeness given no annotations or output schema.

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 zero parameters (empty object), establishing baseline 4 per rubric. Description appropriately doesn't invent parameters, though phrase 'across one or more batch IDs' could confuse slightly by implying input criteria when describing output scope; however, no parameter documentation is required given empty schema.

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?

Clear specific verb 'Aggregate' with resource 'post-migration summary' and explicit field list (totalSubmitted, succeeded, failed, duration). Distinguishes from siblings like migration_getBatchStatus by emphasizing cross-batch aggregation and sign-off use case, though could more explicitly contrast with single-batch queries.

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?

Provides positive usage context ('Suitable for deployment sign-off records') indicating when to use (post-migration validation). Lacks explicit exclusions or named alternatives—doesn't clarify when to use migration_getBatchStatus vs this aggregation tool.

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