calculate_radioactive_decay

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

Discloses the mathematical formula and return value, but no annotations provided. For a pure computation tool, this is adequate but does not go beyond inherent behavior.

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 with purpose, includes formula and references. No unnecessary words.

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?

Simple tool with clear inputs/outputs; mention of related calculators via list_bundles adds completeness. Could mention output units, but schema coverage and return description suffice.

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 covers all three parameters with descriptions. The description adds the formula relating them, which provides additional meaning beyond the schema's 'Initial amount', 'Half-life', 'Time elapsed'.

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 computes remaining quantity after radioactive decay, with specific use cases (physics, carbon dating) and the explicit formula. Distinguishes well among many 'calculate_' siblings.

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 physics or carbon dating and directs to list_bundles for related science calculators. Lacks explicit when-not-to-use, but context is sufficient.

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