calculate_cat_pregnancy

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

No annotations provided, so description must disclose behavior. It mentions gestation period, returns due date window and milestones. For a read-only calculator, this is adequate; no destructive or unexpected side effects.

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?

Two concise sentences, front-loaded with action. Every sentence adds value: what it does, who it's for, inputs, outputs, and related tools. No fluff.

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 one parameter, full schema coverage, and an output schema, the description says enough: purpose, gestation range, target user, output (window and milestones), and pointer to related calculators. Covers all needed context.

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%, so baseline is 3. Description adds 'Returns due date window and milestones' but doesn't enhance the single parameter's meaning beyond schema's 'Mating date YYYY-MM-DD'. Acceptable.

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 specifies the tool's function: compute cat due date from mating date, with gestation range. It targets breeders and distinguishes itself from sibling tools like calculate_dog_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?

It states 'Use for breeders' and explains inputs and outputs. It references list_bundles for related calculators, offering guidance on alternatives. No explicit 'when not to use,' but context implied.

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