list_preset_groups

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is known without the text. The description adds a genuinely useful auth detail ('No token required'), which is not conveyed by the annotations and matters for callers deciding whether to authenticate.

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 compact sentence with the resource front-loaded and the endpoint and auth note appended. It wastes no words, though the phrasing is terse enough to be slightly cryptic about what a 'preset group' actually is.

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 no-param read-only listing tool with annotations covering the safety profile and no output schema, the description is minimally adequate. It omits any indication of what the returned group objects contain or how they relate to presets, which would help an agent choose among the preset siblings.

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 there is nothing for the description to disambiguate; per the baseline rule this scores 4. No parameter guidance is needed or missing.

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?

Identifies the resource ('preset groups for catalog categories') and even names the underlying endpoint ('presets/groups'), but the verb is implicit and it never distinguishes this from the closely related siblings list_presets, get_preset, and search_presets. An agent can guess this is a listing endpoint, but the distinction from list_presets is left to inference.

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 use this tool versus list_presets or the other preset tools, and no prerequisites or exclusions. The only guidance is the parenthetical endpoint path, which describes location rather than selection criteria.

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