calculate_caffeine_intake

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

Describes inputs (list of drinks with type/quantity) and outputs (total mg, % of limit, time-of-day distribution), which goes beyond schema. No hidden behaviors, appropriate for a calculator.

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 efficient sentences: purpose, usage, and reference to alternatives. No unnecessary words; front-loaded with key information.

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 inputs, outputs, and safe limit. References related tools. For a simple calculator with a strong schema, the description is fully adequate.

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?

Adds value by summarizing input structure and clarifying return values (total mg, % of limit, distribution) beyond the schema's enum and exclusiveMinimum constraints.

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 the tool tracks caffeine intake against a daily limit, with specific verb 'track' and resource 'caffeine intake'. Distinguishes from many sibling calculators by focusing on caffeine monitoring.

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 to use for monitoring coffee/tea/soda consumption and directs to list_bundles for related cuisine calculators, providing good context and alternative.

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