calculate_cat_food

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, limitations, or assumptions. It only states the calculation purpose and output format.

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 two sentences, no redundant information, and focuses on the essential purpose and a pointer 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 simplicity of the tool and the presence of an implied output schema, the description covers the basic functionality. However, it lacks details on input units (e.g., kg for weight), enum meanings, and any formula assumptions, leaving some gaps.

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?

The description mentions the three inputs ('weight, age and lifestyle') but does not explain their allowed values, units, or constraints beyond what the schema already provides. With 0% schema coverage, it only partially compensates.

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 that the tool calculates daily cat food quantity and mentions the output format ('Returns: {kcal_per_day}'). It distinguishes from siblings by specifying 'cat food' and referencing list_bundles for other animal calculators.

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 provides minimal guidance: it suggests looking at list_bundles for related calculators, but does not explicitly state when to use this tool over alternatives like calculate_dog_food 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.