convert_to_household_measure

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

With no annotations provided, the description carries the full burden. It only mentions the conversion and nutrient attachment, but does not disclose whether the conversion is approximate, requires a known food database, or imposes input constraints. This is a minimal behavioral disclosure.

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 a single sentence with no fluff, front-loading the conversion purpose before mentioning the nutrient attachment. It is appropriately sized for the tool's simplicity.

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?

The description is minimal; the output schema likely covers return format, but the description lacks input prerequisites, usage context, and any caveats about approximations. For a simple 2-param tool, this is incomplete.

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 0%, so the description must compensate. It mentions grams ('克重') and the resulting portion, but does not define what 'food' should be or any constraints on the grams value. Parameter meanings are only partially conveyed.

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 gram weights to household measures (half bowl, palm, spoon) and attaches nutrient information for that portion. This specific verb-resource pairing distinguishes it from sibling tools like lookup_food_nutrients or sum_diet_intake.

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 when conversion to household measures is needed, but it does not explicitly state when to use this over alternatives or mention any exclusions. No sibling tools are referenced, so guidance is only implied.

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