List thread members

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

The annotation readOnlyHint=true already declares the read-only nature. The description adds no additional behavioral context such as pagination, permission requirements, or the distinction between thread members who can view vs. have joined. It simply restates the title in question form without new information.

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 short sentence with no wasted words, achieving high conciseness. However, it is so minimal that it borders on under-specification, but it does not repeat the tool name exactly and is efficiently front-loaded.

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?

With a simple list operation, readOnlyHint, and full schema coverage, the description provides the minimum viable context. It lacks alternative tool references and output details, but for a straightforward read-only list, this may be adequate.

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 provides 100% coverage with descriptions for both 'guild' and 'thread', so the baseline is 3. The description adds no parameter-specific semantics, so the score remains at baseline.

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 'Who is in a thread' clearly conveys that the tool lists members of a thread, distinguishing it from sibling tools like list_members (guild members) and get_role_members (role members). However, it uses a question format rather than an explicit imperative verb like 'list', which slightly reduces specificity.

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 versus alternative member-listing tools such as list_members or get_role_members. The description only states what it does, not the appropriate context or exclusions.

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