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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered and the description adds an enumeration of touchable fields. But it says nothing about the critical mutation behavior: whether unspecified fields are preserved or whether omitting a field clears it. With annotations carrying the safety burden, a 3 is fair.

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 front-loaded sentence that opens with the use condition and then enumerates the fields, with no filler. It is dense but every clause carries distinct field information.

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 an 11-parameter mutation tool with no output schema, the description covers which fields exist but omits the partial-update semantics that an agent needs to call it safely. Nothing explains what happens to fields the caller does not send, which is the main remaining gap.

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 only 9%, so the description is doing real work by mapping 10 of the 11 parameters to plain-language concepts ("bench notes" → personalNotes, "favourite star" → favorite, "pin" → pinned, "bottle size" → bottleSizeMl). It does not address the required formula argument beyond what the schema already documents, nor the kind enum values, so it stops short of a 5.

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 names specific updatable attributes (name, description, kind, folder, favourite, pin, concentration, IFRA category, bottle size), so the agent knows this is a metadata-mutation tool. However, it never distinguishes itself from the sibling edit_formula, which by name appears to do something similar, leaving ambiguity about which to pick.

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?

"Use this when the user wants to rename a formula or change its description..." gives clear intent-based triggers that map to user phrasing. There are no exclusions, though, and the natural alternative (edit_formula) is not mentioned, which would have made the guidance complete.

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