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

No annotations are provided, so the description must cover behavioral traits. It correctly states it computes a value and returns joules, but does not mention any edge cases, performance characteristics, or side effects. As a pure function, the transparency is acceptable but minimal.

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 a single sentence that includes the formula, input units, and output unit, plus a reference to related calculators. It is highly concise and front-loads the essential 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?

Given that there is an output schema (context says yes), the description covers the necessary details: formula, inputs, output unit, and use cases. It is complete for a simple calculation tool. No major gaps.

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?

The input schema already provides descriptions for both parameters (mass_kg and velocity_ms), so the description adds little new information beyond restating them and providing the formula. Schema coverage is 100%, so the description is not required to compensate.

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 explicitly states the tool computes kinetic energy using the formula KE=½·m·v², specifies inputs in kg and m/s, and output in joules. This clearly differentiates it from other physics calculators in the same suite.

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?

It suggests use cases (physics, vehicle safety) and directs users to list_bundles for related 'science' calculators, providing context for when to use alternatives. However, it does not explicitly exclude any use cases or mention specific alternative tools.

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