migration_getBatchStatus

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

No annotations are provided, so the description carries the full burden. It partially discloses behavior by listing the specific status fields returned (totalJobs, jobsCreated, jobsCompleted, jobsFailed, suspended), which hints at the output structure. However, it lacks information about error handling (e.g., batch not found), performance characteristics, or whether the operation is read-only (implied by 'Get' 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?

The description is a single, efficient sentence that front-loads the purpose ('Get current status') and appends the specific field details. Every word earns its place with no redundancy or boilerplate.

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?

With no output schema provided, the description partially compensates by enumerating the returned fields. However, given the empty input schema (0 properties), the description fails to explain how to identify which specific batch to query—an essential gap for a tool targeting a 'single' resource.

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?

The input schema contains 0 parameters, which triggers the baseline score of 4 per evaluation rules. With no parameters to describe, there is no additional semantic information needed beyond the baseline.

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?

The description uses a specific verb ('Get') and resource ('status of a single migration batch') and enumerates the specific fields returned (totalJobs, jobsCreated, etc.), which helps distinguish it from sibling list operations. However, it does not explicitly differentiate from 'migration_getBatchSummary' or 'migration_getBatchFailures', leaving some ambiguity about which status tool to use.

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?

The description provides no guidance on when to use this tool versus alternatives like 'migration_getBatchSummary' or 'migration_getBatchFailures', nor does it mention prerequisites or conditions for use. The agent is given no signal for tool selection strategy.

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