members

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

With no annotations, the description carries the full behavioral burden and does not meet it. It does not disclose whether this is read-only (implied but unstated), whether it requires admin rights, whether results are paginated or truncated, or what fields come back. For a listing tool with zero annotation coverage this is a significant gap.

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 short sentence with the action front-loaded and no wasted words. It is efficient, though the terseness edges toward under-specification rather than optimal 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?

No output schema, no annotations, and no parameters means the description is the only source of information, and it omits the critical question of which group or channel is being listed. It also says nothing about result shape or limits, so an agent cannot confidently invoke it.

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 declares zero parameters, so per the baseline there is nothing for the description to document or compensate for. No parameter syntax is needed, though the description could have explained how the target group is otherwise determined.

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 members of a group or channel'. This distinguishes it from siblings like contacts, block_list, or dialogs, which deal with different entities. It stops short of 5 because it never clarifies how the target group or channel is identified, which matters given the tool takes no parameters.

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 on when to use this versus alternatives such as contacts or block_list, and no mention of prerequisites (e.g., membership in the group, or whether it works on channels as well as groups). The only hint is the phrase 'group or channel', which implies scope but not selection criteria.

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