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

Annotations already declare readOnly=true, destructive=false, and openWorld=true, so safety is covered. The description adds a concrete behavioral constraint the annotations do not carry: a rate limit of 1 request every 3 seconds, which directly shapes how an agent should batch calls.

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?

Two sentences, front-loaded with what is returned and followed by the throttle constraint and endpoint. The enumeration is dense but every item conveys real payload content, so there is little 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?

With no output schema, the description must describe return contents and it does thoroughly, plus it discloses the rate limit. Only minor gaps remain, such as behavior on an invalid or unknown id.

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% and the single ingredient_id parameter is documented there, including its origin (from parsley_list_ingredients). The description adds no further semantics about the id, so the baseline of 3 applies.

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?

States a specific verb+resource (get one ingredient) and enumerates exactly what it returns: unit conversions, supported units, tags, supply options with supplier/SKU/pack size/cost, and preparations with yield. That level of detail clearly separates it from parsley_list_ingredients and the menu/event 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 description gives an operational rule ('fetch ingredients one at a time' due to the 3-second throttle) and the schema note points back to parsley_list_ingredients as the id source, but there is no explicit statement of when to prefer this over alternatives or what preconditions apply beyond the id requirement.

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