yougile_list_group_chats

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read nature is covered. The description adds no additional behavioral context such as pagination behavior, result limits, or filtering options; it only restates the resource scope without revealing any constraints.

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 a single, clear, front-loaded sentence with no wasted words. It effectively communicates the purpose without any filler.

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 read-only list tool with strong annotations and full schema coverage of parameters, the description is mostly complete. It lacks explicit mention of pagination or filtering, but these are adequately covered by the schema, so the description remains sufficient for an agent to understand the tool's role.

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 input schema covers all three parameters (limit, title, offset) with a 100% description coverage, so the description does not need to explain them. However, it also does not add any extra meaning, such as noting that 'all' results can be filtered or paginated, so it earns the baseline score.

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 'List all group chats in the company,' using a specific verb and resource. It distinguishes itself from siblings like yougile_get_group_chat, yougile_create_group_chat, and yougile_update_group_chat by focusing on listing all group chats.

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 offers no guidance on when to use this tool versus alternatives, no mention of alternatives like yougile_get_group_chat, and no exclusions or prerequisites. It simply states what it does, leaving usage context to the agent to infer.

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