wechat_members

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

With no annotations, the description carries the full burden but only states 'List members'. It does not disclose if the operation is read-only (safe to call), what format the members are returned in, or if there are requirements like authentication or group membership. This is insufficient for an agent to understand the tool's behavior.

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 single sentence is highly concise with no redundant words. However, it sacrifices substance for brevity; a slightly longer description could provide necessary details without losing conciseness.

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?

Given the tool has a single required parameter, an output schema, and many siblings, the description is too minimal. It should at least clarify that the output is a list of member identifiers or profiles for the specified group. The current state leaves important gaps in understanding.

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 0% description coverage for the required parameter 'group_name', and the description adds no semantic meaning. The agent is left guessing whether 'group_name' refers to a display name, internal ID, or exact string match. No examples or format hints are given.

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 'List members of a WeChat group' clearly states the verb (list) and resource (members of a specific group), distinguishing it from siblings like wechat_contacts and wechat_sessions. However, it could be more explicit that it's for a single group identified by name.

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 provided on when to use this tool vs siblings like wechat_contacts or wechat_search. There is no mention of prerequisites, such as being a member of the group, or alternatives for broader member queries.

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