List birth events

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are 'saved' events (implying drafts/previews are excluded) and that pagination is bounded, but says nothing about ordering, default page size, or total counts.

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?

A single front-loaded sentence with no filler; pagination and filtering are surfaced immediately. It is efficient, though slightly too terse given the parameter coverage gap.

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 and 0% schema description coverage on 4 parameters, the description carries the burden and falls short. An agent still lacks default page size, sort order, whether farm_id or animal_id is required for meaningful results, and what a birth event record contains.

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 0% across 4 parameters, so the description must compensate and largely does not: it mentions filtering by 'dam or offspring' (loosely animal_id) but omits farm_id entirely and gives no offset/limit semantics for skip/take. The mapping from 'dam/offspring' to animal_id is left for the agent to guess.

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 (List) and resource (saved birth events), and the sibling names (get_birth_event, preview_birth_event, confirm_birth_event) make the list-vs-single-vs-write distinction inferable. However the stated filters ('dam or offspring') do not name the actual schema fields (farm_id, animal_id), which blurs exactly what can be filtered on.

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?

No guidance on when to call this versus get_birth_event, preview_birth_event, or the other list_* tools. The word 'saved' hints at excluding drafts/previews, but no alternative is named and no exclusions or prerequisites are given.

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