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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description only needs to add extra context. It does so by warning that the conversion is approximate and by citing the source of the conversion values.

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 core behavior is stated in the first clause, followed by a compact ingredient legend and a source URL. No sentence is wasted.

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 two-parameter, simple read-only conversion with a full input and output schema, nothing essential is missing: accepted ingredients are enumerated, the approximation caveat is present, and a source is provided for verification.

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%, so the baseline is 3; the description adds value by expanding the terse enum literals into full ingredient names and clarifying special cases such as 'packed brown sugar' and 'uncooked rice'. The cups parameter's meaning is already clear from 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 uses a specific verb ('Convert'), resource ('US cups of a common baking ingredient to grams'), and qualifies the result as approximate. Listing exact ingredient keys distinguishes it from generic volume/weight converters among the siblings.

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 phrase 'common baking ingredient' implies the intended use case, but the description never explicitly says when to choose this tool over sibling converters or when not to use it. Usage guidance is left to inference rather than stated.

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