convert_weight

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

No annotations are provided. The description states it 'Returns converted mass' but does not disclose that it is a pure calculation with no side effects, permissions, or rate limits. Since it is a simple conversion, the lack of behavioral details is a minor gap.

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?

Three sentences are efficient and front-loaded with the core purpose. Every sentence adds context (use cases, parameter list, output, reference to related tools). No wordiness.

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 the output schema exists and the tool is simple, the description covers purpose, parameter structure, and use cases. It references related tools for additional context. Adequate for a straightforward conversion tool.

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 all three parameters. The description redundantly lists them ('value, from, to') and restates units already in the enum, adding minimal semantic value 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?

The description clearly states the tool converts weight/mass between specific units (kg, g, mg, lb, oz, st, tonne). It is distinct from other conversion tools like convert_angle or convert_area, though it does not explicitly differentiate itself from the broader set of converters.

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 scenarios ('cooking, shipping, or fitness') and advises to 'See list_bundles for related conversions calculators', which guides the agent to alternatives. However, it lacks explicit when-not-to-use guidance.

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