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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and idempotency profile is fully covered. The description adds one genuinely new behavioral fact — the farmId + apiKey authorization requirement — but says nothing about pagination behavior or result shape despite eight parameters including limit and cursor.

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 short, front-loaded sentences with no filler; the purpose leads and the requirement follows. It is arguably too terse for an eight-parameter list tool, but that is a completeness issue rather than a structure flaw.

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?

There is no output schema, so the description could reasonably be expected to say more about what a returned hatch batch contains, and it omits any mention of pagination despite having limit/cursor parameters. Annotations carry the safety profile, leaving the description merely adequate rather than complete.

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?

Schema description coverage is 100%, so every parameter (limit, cursor, status, startDate, endDate, variety, incubator, farmId) is already self-documented. The description echoes only farmId and adds no filter semantics, date format guidance, or interaction rules beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Retrieve incubation and hatch batches"), which is enough to separate it from write siblings like log_hatch_set and log_hatch_result. It does not, however, distinguish itself from the closely-named read sibling get_bird_batches, which an agent could plausibly confuse it with.

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 only guidance is a prerequisite ("Requires farmId and apiKey authorization"), which is a precondition rather than a when-to-use statement. No alternatives are named and no exclusions are given, even though get_bird_batches and get_egg_collections sit in the same domain.

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