List Groups Preferences

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get Group Preferences' merely restates the tool's purpose and does not disclose read-only behavior, authentication requirements, scope, or any other behavioral traits beyond what the name already implies.

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 extremely terse, but this is under-specification rather than effective conciseness. While it is front-loaded, it is so minimal that it fails to provide useful information beyond the tool name.

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?

The tool is relatively simple and has an output schema, so return values do not need explanation. However, the description lacks essential context such as the scope of 'groups', whether this returns all groups or the current group's preferences, and how the accept-language parameter affects the response.

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 has one parameter, accept-language, with 0% schema description coverage, and the description does not mention it at all. The parameter's name is somewhat self-explanatory, but the description adds no meaning or usage context for it.

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 states a clear verb ('Get') and resource ('Group Preferences'), and the title/name clarify that this is a list operation. It is distinguishable from the sibling update_groups_preferences by its read verb, though it does not explicitly state the scope (e.g., current group vs. all groups).

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 is given about when to use this tool versus alternatives. The sibling list includes update_groups_preferences and list_households_preferences, which are closely related, but the description does not mention them or provide any selection criteria.

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