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

No annotations are provided, so the description carries full burden. It states 'Returns due date and gestation milestones' but provides no details on the format, number of milestones, or any side effects. The species mismatch further reduces 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 concise, with one sentence and a simple listing of inputs and returns. It avoids unnecessary fluff, though the species list could be aligned to schema.

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 that an output schema exists, the description's mention of gestation milestones is adequate but incomplete due to the species discrepancy and lack of detail on available species. The tool's role among many sibling pregnancy calculators is not fully clarified.

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%, so the description must compensate. It lists species but includes horse/cow, which are not in the schema (which has hamster instead). This misrepresentation adds confusion rather than clarity. No additional constraints on mating_date format are given.

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 it computes a due date for animal breeding, targeting breeders. However, it lists species (horse/cow) that do not match the schema enum (dog/cat/rabbit/hamster), creating potential confusion for the agent.

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 mentions 'Use for breeders' and directs to list_bundles for related calculators, implying some context but lacks explicit guidance on when to prefer this tool over species-specific pregnancy calculators (e.g., calculate_dog_pregnancy) or when not to use it.

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