math_unit_converter

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

With no annotations, the description bears full responsibility for behavioral disclosure. It mentions NIST standards (positive) but does not state whether the tool is read-only, has side effects, or requires authentication. Minimal transparency.

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 short (two sentences) and front-loaded with the primary purpose. However, the first sentence includes a redundant 'Menu ID' and 'Unit Converter' that could be trimmed. Minimal waste.

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 4 required parameters, no output schema, and no enum constraints, the description fails to provide complete context on how to invoke the tool correctly. It relies on the user calling describe_tool for full guidance, which does not satisfy standalone 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 description coverage is 0% and parameters lack enum values. The description lists categories and number of units but does not explain how to specify unit values (e.g., abbreviations) or the format of the value parameter. Directs to describe_tool for details, leaving the agent with insufficient guidance.

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 between 60+ units across 9 specific physical categories (length, mass, volume, etc.), using NIST standards. It distinguishes itself from many sibling conversion tools (e.g., currency, binary) by focusing on physical units.

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 implies use for physical unit conversion by listing categories, but does not explicitly state when to use this tool versus alternatives like number base or currency converters. No when-not or alternative tool names are provided.

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