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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The word 'Replace' is consistent with those hints, but the description adds no extra detail such as whether existing ingredients are discarded wholesale, whether other supplement fields are preserved, or how partial failures behave.

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?

A single short sentence with zero waste, but the brevity is achieved by omitting necessary information rather than by efficient phrasing. It is front-loaded but under-specified.

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?

A destructive mutation with a nested-object payload, no output schema, and no annotation-level detail about return values or side effects. The description does not compensate for the empty parameter documentation, leaving the agent guessing about the shape and effect of the call.

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% except for the 'unit' example, and the description says nothing about supplementId or the nested ingredients objects. For a tool whose main parameter is an array of structured ingredient records, the description should at least indicate that the supplied list supersedes the current one.

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 and resource ('Replace the ingredient list of a supplement'), which is clear enough to act on. It does not distinguish itself from the sibling stackwell_update_supplement, leaving ambiguity about which mutation to use for ingredient changes.

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?

No guidance on when to use this instead of stackwell_update_supplement, no prerequisites (e.g. does the supplement need to exist, does the caller need ownership), and no when-not-to-use conditions. The agent must infer everything from the one-line purpose.

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