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

Annotations already cover read-only, idempotent, non-destructive, closed-world. The description adds two facts beyond them: currency is returned as a unit "never the prices" (clarifying data granularity) and that confirmChanges is website-only, an approval-flow constraint the agent cannot act on. The safety profile itself is left to the annotations.

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 long sentence, but it is front-loaded with the resource and then lists return contents in order of relevance. Every clause carries information; the density is justified by the number of settings, though a list format would read better.

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 carries full burden for return values, and it enumerates every field returned, including the enumerated confirmChanges values (off, removals, all). Nothing needed to call or interpret this zero-argument read is missing.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to document or misdescribe.

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?

Names the specific resource (the caller's Glazecalc settings) and enumerates exactly which settings it returns: region, temperature scale, cones, language, weight unit, lead suggestion policy, recipe limit set, currency, and confirmChanges. No sibling tool returns user settings, so an agent can select it unambiguously from the list.

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?

"Settings that matter when talking about glazes" scopes when the tool is relevant, and "it can be changed only there" signals a when-not: don't attempt to modify confirmChanges through tools. It stops short of naming explicit alternatives or preconditions, so not a 5.

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