convert_energy

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

No annotations provided, so description must cover behavior. It mentions returns '{input}' which is vague but output schema exists, reducing the need for detail. Lacks specifics on rounding, precision, or error handling, and the ft-lb unit discrepancy introduces confusion.

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?

Extremely concise: one sentence listing units and use cases, plus a pointer to related tools. No wasted words, front-loaded with 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?

Adequate for a simple conversion tool with full schema coverage and output schema. However, the ft-lb unit mentioned in the description is missing from the input schema enum, which is a significant gap that reduces completeness.

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 100% with descriptions for each parameter. Description repeats 'Inputs: value, from, to' and lists units, adding marginal value. The enum for 'from' and 'to' already defines valid units, so the description does not significantly enhance understanding.

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 it converts energy between specific units (J, kJ, cal, kcal, kWh, BTU, eV, ft-lb). Distinguishes from sibling conversion tools like convert_angle, convert_area, etc. However, the input schema enum does not include 'ft-lb', causing a minor inconsistency.

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?

Provides usage context: 'Use for nutrition, electricity, science.' Also directs to list_bundles for related conversion calculators, indicating alternatives. Does not explicitly state when not to use, but context is clear enough for an AI agent.

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