list_birth_events

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

The description is consistent with annotations (readOnly, idempotent, non-destructive). It adds behavioral detail about bounded pagination and optional filtering by dam or offspring, which is beyond annotations. However, it does not elaborate on response format or ordering, though annotations already cover 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?

One sentence, front-loaded with the core purpose, and no filler. It efficiently communicates what, how (pagination), and optional filters.

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?

For a simple list tool with read-only annotations and explicit pagination defaults in the schema, the description covers the essential usage. It lacks details on return shape and ordering, but given the simplicity and existing annotations, it is sufficiently 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 coverage is 0%, so the description must compensate. It mentions pagination (bounded) and filtering by dam or offspring, which maps to skip/take and animal_id, but it does not explicitly map farm_id or clarify which parameter corresponds to dam vs offspring. Parameter names themselves are self-explanatory (farm_id, animal_id), so the description adds moderate value.

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 ('List') and resource ('saved birth events'), and distinguishes itself from siblings like get_birth_event (single event) and preview_birth_event (preview). Mentioning saved events implies it lists already confirmed/recorded events, which separates it from preview/confirm tools.

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 implies when to use the tool (to list saved birth events) but does not explicitly contrast it with alternatives like get_birth_event or list_farm_tasks. The usage is clear from the purpose, but there is no explicit when-not or alternate routing.

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