calculate_pet_medication_dose

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

No annotations are provided, so the description must fully disclose behavior. It mentions returning total mg and tablet count but omits the optional parameter concentration_mg_per_ml, which affects output. No discussion of safety, prerequisites, or limitations is included.

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 front-loaded sentences with no wasted words. It efficiently states purpose, usage, inputs/outputs, and a reference to related tools.

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 the optional concentration parameter and the existence of an output schema, the description does not fully explain how the optional input affects results or what additional outputs may appear. It only mentions 'total mg and tablet count', which may be incomplete.

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 explain parameters. It only names two inputs (weight kg, dose mg/kg) while the schema has three parameters, failing to mention the optional concentration_mg_per_ml and its significance.

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 the tool's purpose: 'Compute veterinary medication dose by pet weight (mg/kg)'. The verb 'compute' and the specific resource 'veterinary medication dose' distinguish it from sibling calculator tools like 'calculate_pet_food_portion' or 'calculate_dog_food'.

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 medication administration', providing clear context. However, it does not specify when not to use it or explicitly mention alternatives; the reference to 'list_bundles' for related calculators is vague.

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