list_tool_groups

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

The readOnlyHint annotation already covers the safety profile, but the description adds useful output context: it reports every group, its tool count, and whether it is loaded natively or reached via search_tools + invoke_tool. It does not mention ordering, pagination, or result format details, but for a no-parameter read-only discovery tool this is solid additional transparency.

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 front-loaded sentence with no wasted words. It starts with the verb 'List' and packs the resource, returned count, and load-mode semantics into one efficient sentence.

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 simple zero-parameter, read-only listing tool with no output schema, the description adequately explains what will be returned and the native/on-demand distinction. The main gap is that it does not explicitly guide the agent on when to use this versus search_tools, but the core call semantics are complete.

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 has zero parameters, so there are no parameter semantics to explain. The empty schema is consistent with the description, and per the rubric a zero-parameter tool receives a baseline of 4 when the description does not need to compensate for undocumented inputs.

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: 'List every WebCake tool group.' It also names the returned attributes—tool count and native vs on-demand loading via search_tools + invoke_tool—so it is clearly distinguishable from sibling tools like search_tools, which operate on tools rather than 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?

The description implies this is a discovery tool for understanding available tool groups and their access mode, but it never explicitly says when to call it or when to prefer it over search_tools/invoke_tool. There are no exclusions or prerequisites, so usage is only implied rather than stated.

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