momentum_calc

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

With no annotations provided, the description adequately discloses the tool is a non-destructive calculator. It lacks edge-case handling but is sufficient for a simple physics 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 concise with only three sentences, no wasted words, and front-loads the core purpose and formula. Parameter list is well-organized and readable.

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?

Despite no output schema shown, the context confirms its existence. The description fully covers the input behavior for a 3-parameter calculator, making it complete for its complexity.

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 property descriptions are empty (0% coverage), but the tool description fully explains each parameter (mass in kg, velocity in m/s, momentum in kg·m/s) and the convention of leaving unknown as 0, adding 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 states 'Calculate momentum, mass, or velocity using p = mv', clearly identifying the tool's function and the physical formula. This distinguishes it from sibling tools like force_calc or kinetic_energy_calc.

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 explains that parameters should be left as 0 if unknown, implying exactly two values must be provided to compute the third. It provides implicit guidance but could explicitly state the usage rule.

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