netintel_convert

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

With no annotations, the description carries the full burden, and it does add real behavior: auto-detection of unit category and handling of US/imperial ambiguity. However it says nothing about error behavior for unsupported or mismatched units, precision/rounding, or what the `system` and `base` parameters change in behavior.

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?

Front-loaded with the core action and an efficient list of supported categories in a single sentence. The trailing ellipsis suggests the text is truncated, which is the only structural blemish.

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 5-parameter tool with zero schema descriptions, no annotations, and no output schema, the description is too thin. It omits any explanation of the non-obvious `base` and `system` parameters and gives no indication of return shape or failure modes.

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 description coverage is 0% across 5 parameters, and the description never explains `value`, `from`, `to`, `base`, or `system`. The auto-detect claim loosely gestures at `system`/`base` but gives no syntax, allowed values, or defaults, so the description does not compensate for the schema gap.

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?

States a specific verb and resource ('Convert any physical measurement to another') and enumerates the supported categories, which separates it from the money-oriented siblings like netintel_currency_exchange and netintel_crypto_price. An agent can tell what this tool does without opening the schema.

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?

Usage is only implied by the category list ('length, mass, volume, temperature...'), which lets an agent infer the domain but gives no explicit when-to-use or when-not-to-use guidance. No alternative tool (e.g. currency conversion) is named or excluded.

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