convert_oilfield_units

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

No annotations are provided, so the description must disclose all behavioral traits. It describes what conversions are supported but does not mention case sensitivity, aliases, error handling (e.g., invalid units), output format, or whether units are case-sensitive. This leaves significant ambiguity for the AI agent.

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 adequately sized with a clear first sentence, but the long bullet list of units, while helpful, could be more concise. Every sentence serves a purpose, but the list could be summarized to reduce verbosity.

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 conversion tool with many supported units, the description covers unit categories and examples adequately. There is an output schema, so return values need not be described. However, it lacks details on edge cases like unit aliases or case sensitivity. Overall, it is fairly 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?

The input schema has 0% description coverage, so the description compensates by listing the three parameters with examples: 'value: Numeric value to convert.', 'from_unit: Source unit (e.g. 'bbl', 'psi', 'API').', 'to_unit: Target unit (e.g. 'm3', 'kPa', 'SG').' This adds meaning beyond the bare schema, although it could be more comprehensive.

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 'Convert between oilfield and SI units' with a specific verb and resource. It lists supported unit categories (volume, rate, pressure, etc.) and many specific units, making the purpose unambiguous. It distinguishes itself from sibling tools like list_oilfield_units (which only lists units) and various calculation tools.

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 implicitly indicates usage for conversion tasks but does not explicitly state when to use this tool versus alternatives like list_oilfield_units or other calculation tools. It lacks explicit 'when to use' and 'when not to use' guidance, though the context is clear from the function name.

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