Set list total display unit

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral detail: the setting does not affect the units returned to the agent; responses always use grams. However, it doesn't specify whether the setting is global or per-list, which is a minor gap given the schema only contains 'unit'.

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 description is two concise sentences, front-loaded with the action and resource, then immediately clarifying the crucial scoping vs. MCP responses. No filler or redundancy.

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 one-parameter setter with no output schema, the description adequately explains the effect and the key distinction from MCP response units. It doesn't mention global scope, but the absence of a list ID in the schema implies it. Overall, it's complete for the tool's simplicity.

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 schema description coverage is 0%, but the description compensates by explaining the meaning of the 'unit' parameter: it sets the display unit for list totals. It also lists the valid values (oz/lb/g/kg), which matches the enum and adds context beyond raw 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 clearly states the tool sets the unit LighterPack's UI uses to display list totals, enumerates the allowed units (oz/lb/g/kg), and distinguishes it from item-level unit settings. The verb 'sets' plus resource 'display unit for list totals' is specific and differentiates from siblings like set_item_unit.

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 explicitly clarifies that this tool affects only the UI display, not the units reported back by the MCP server. This provides clear guidance on when to use it (to change UI display) and when not to (if expecting different response units). It doesn't name alternatives but the context implies a distinction.

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