calculate_pet_medication_dose

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

No annotations provided. Description covers inputs and outputs (total mg, tablet count) but omits behavioral details like whether the tool assumes a standard tablet strength or what concentration_mg_per_ml does. As a calculation tool, it's likely safe, but transparency is limited.

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?

Three sentences, front-loaded purpose and usage. Efficient but could be more structured with explicit headings or lists. Every sentence serves a purpose.

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?

Covers primary use and basic outputs, but missing explanation for the optional concentration parameter and how tablet count is derived. Output schema exists, reducing need for detailed return values, but the omission weakens completeness for a 3-parameter tool.

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% (no parameter descriptions). The description lists 'weight kg' and 'dose mg/kg' corresponding to two required parameters but does not mention the optional concentration_mg_per_ml parameter or its role, leaving incomplete semantic coverage.

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?

Clearly states 'Compute veterinary medication dose by pet weight (mg/kg)' with specific verb and resource. Differentiates from sibling pet tools like calculate_pet_bmi or calculate_pet_food_portion.

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?

Explicitly says 'Use for medication administration', providing clear context. References list_bundles for related calculators but does not specify when not to use or exclude alternatives.

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