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

Adds substantial context beyond the weak annotations: a hard cap of 40 results, the warning that text matching is not the complete candidate set, and explicit non-actions (will not join, invite, or read group messages). These disclaimers are genuinely useful, though the description's read-only framing sits in mild tension with readOnlyHint=false.

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 dense, front-loaded passage with no filler; scope, mode switch, result limit, matching caveat, and non-actions are all stated economically.

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-value details are rightly omitted, and the description covers scope, limit, matching caveat, and non-actions for a 2-parameter list tool. Only the q parameter's semantics are left under-specified.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains discover=true well, but the q parameter is only obliquely implied by the 'text matching is not the complete candidate set' caveat, with no statement of what q matches against.

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 (组局、群聊 / 公开组局) and separates two modes: the user's joined/invited groups vs. publicly discoverable ones. It is very clear in isolation, but never names or contrasts with the nearby siblings (e.g. fitmeet_group_get, fitmeet_conversations_list), so it falls short of full sibling differentiation.

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?

Gives a clear condition for the two modes: default queries the caller's own joined/invited groups, and discover=true switches to searching public, externally-discoverable groups. No when-not-to-use or explicit alternative is named, but the mode-selection context is unambiguous.

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