calculate_dog_pregnancy

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

With no annotations, the description carries the full burden. It states the tool returns 'due date window and milestone dates', which is helpful. However, it does not disclose behavior such as input validation, error handling (e.g., for invalid dates), or any side effects. The simple nature of the tool lowers the need, but more specificity 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 concise sentences. The first sentence delivers the core purpose immediately, and each subsequent sentence adds value without redundancy. No wasted words.

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?

Given a single required parameter, no annotations, and the existence of an output schema, the description adequately covers the tool's functionality and return value. It could mention the output schema or provide an example, but for a simple date calculator, 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 100% with the schema already describing the parameter as 'Mating date YYYY-MM-DD'. The description adds minimal context by mentioning 'gestation 63 days', but does not elaborate further on the parameter format or constraints. With high coverage, a baseline of 3 is appropriate, and the description adds just enough to meet it.

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?

Description clearly states the tool computes dog due date from mating date with a 63-day gestation period. It specifies the verb 'Compute' and resource 'dog due date', effectively distinguishing it from sibling tools like 'calculate_cat_pregnancy' or 'calculate_pregnancy_due_date'.

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 tool is described as 'Use for breeders', providing a target audience. It also directs to 'list_bundles for related 'animaux' calculators'. However, it does not explicitly mention when not to use this tool or compare it to similar sibling tools like 'calculate_dog_age' or 'calculate_breeding_due_date'.

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