calculate_breeding_due_date

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

No annotations are provided, so the description must carry behavioral disclosure. It states that the tool 'returns due date and gestation milestones,' which is adequate for a calculator. However, it does not explicitly state it is read-only or non-destructive, though the 'calculate' prefix implies computation. Adding notes on safety or side effects would improve transparency.

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 three sentences: first defines the purpose, second indicates target users, third lists inputs, outputs, and a reference. No redundant information. Efficiently structured and front-loaded.

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?

Despite having an output schema, the description is incomplete: it fails to note that the species parameter must be one of the enum values (dog, cat, rabbit, hamster) and includes incorrect species. It also does not address how this tool relates to similar sibling tools like calculate_dog_pregnancy. The schema mismatch is a significant gap.

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 description adds context by naming the parameters ('species (dog/cat/horse/rabbit/cow), mating date'), but the listed species are inconsistent with the schema's enum (which lacks horse and cow but includes hamster). This misalignment reduces the value of the added semantics. The mating date parameter is accurately described but the format is already in the 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?

The description clearly states its purpose ('Compute due date for animal breeding'), but it lists species (horse, cow) not present in the schema, which contradicts the enum (dog, cat, rabbit, hamster). This inaccuracy undermines clarity and could mislead agents.

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 says 'Use for breeders' and points to list_bundles, but it does not distinguish this tool from sibling tools like calculate_dog_pregnancy or calculate_cat_pregnancy, which serve overlapping purposes. No guidance on when to choose this multi-species calculator over species-specific ones.

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