kinetic_energy_calc

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

No annotations provided, so description must carry the burden. It mentions the formula but does not disclose behavior for edge cases (e.g., all zeros, negative values, underdetermined system). Missing return format or error conditions.

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?

Concise with one-line purpose and parameter list. No wasted words, though the bullet list could be integrated into a single paragraph for better flow.

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?

Adequate for a simple calculation tool, but lacks explanation of edge cases or response structure. Output schema exists, so return values are covered, but completeness is moderate given missing operational details.

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 coverage is 0%, and description fully compensates by providing units (kg, m/s, J) and usage instructions (leave 0 if unknown) for each parameter, 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?

Clearly states the tool calculates kinetic energy, mass, or velocity using the formula KE = ½mv², but does not differentiate from sibling physics calculators like force_calc or momentum_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?

Implies usage by instructing to leave unknown parameters as 0, but lacks explicit when-to-use or comparison with alternatives. No guidance on prerequisites or limitations.

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