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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the agent knows this is a safe, non-mutating operation. The description adds that it handles various units and includes triggers, but does not mention ingredient-specific density behaviors or output precision. Given the annotations, this level of added context is adequate but not enriching.

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 compact: one purpose sentence plus a clear trigger list. Every element earns its place—the triggers are practical and directly aid selection. There is no redundancy or fluff.

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 straightforward conversion tool with complete schema annotations, the description provides sufficient context—unit examples, trigger phrases, and clear scope. The lack of an output schema is acceptable since the return value is likely simple and predictable. Not quite a 5 because it omits any note about unsupported unit handling or precision.

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 100% coverage with descriptions for all four parameters, including examples (e.g., fromUnit lists 'cups', 'tbsp', 'oz'). The description's unit list adds minimal new meaning beyond the schema. A baseline of 3 is appropriate since the schema carries the semantic weight.

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 opens with 'Convert between cooking measurement units', a specific verb+resource, and enumerates unit types (cups, tablespoons, grams, etc.). This clearly distinguishes it from sibling tools like cooking_get_substitutions or nutrition_analyze, which address different tasks.

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 'TRIGGERS' section provides explicit example user queries ('how many grams in a cup', 'convert tablespoons to cups') that signal when to use the tool. This is clear context for selection, though it does not explicitly mention when not to use it or name alternative tools.

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