List Groups Labels Empty

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

No annotations are provided, so the description carries the burden; 'Returns a list' implies a safe read, but it does not disclose scope (household or group), whether results are permission-filtered, ordering, or whether it paginates. The unused-label filter is the one genuinely behavioral detail and it is stated precisely.

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?

One sentence with zero filler, and the key qualifier ('not used by any food or shopping list item') is placed where it is read first. It is short enough that it could afford one more clause of guidance without becoming bloated.

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?

An output schema exists, so return values need not be explained, and the purpose sentence is adequate for a zero-required-parameter tool. However, with no annotations and an undocumented parameter, the definition leaves the agent guessing about scope and the meaning of accept-language.

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 single parameter (accept-language) has 0% schema description coverage and is never mentioned in the description, so nothing tells an agent that it is an optional localization hint or what it affects in the results. With a low-coverage schema the description should compensate, and it does not.

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 (returns labels) plus the defining filter: labels unused by any food or shopping list item. That is a clear purpose, but it never names the closely related sibling list_groups_labels (all labels), so an agent must infer the distinction from the '_empty' suffix convention seen in other empty-list 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?

There is no statement of when to call this instead of list_groups_labels, no mention that it is a read-only cleanup/audit operation, and no prerequisites or exclusions. The agent gets a definition but no routing guidance among dozens of list_* siblings.

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