calculate_density

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

Since annotations are absent, the description bears full responsibility. It states the computation logic and formula but does not mention unit handling, potential error cases, or behavioral nuances beyond the basic calculation.

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 sentences, front-loading the purpose and formula, then usage context. Every sentence is informative and there is no redundancy.

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?

For a simple calculator tool, the description fully covers inputs, outputs, and application areas. It also references a related bundle for more context. With an output schema present, no further detail is needed.

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 descriptions are minimal but present (e.g., 'Mass kg'). The description adds the crucial logic that any two parameters are needed and the third is computed, which adds significant meaning beyond the schema.

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 it computes density, mass, or volume given the other two, using the formula ρ=m/V. It distinguishes itself from many sibling calculators by specifying its unique function.

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 explicitly provides context for use ('materials, chemistry, fluid dynamics') and specifies the input/output pattern (any 2 of mass, volume, density returns the third). It lacks explicit exclusions or alternatives, but the guidance is clear.

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