list_topic_members

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

With no annotations, the description carries the full burden of behavioral disclosure. It states a read-only action ('List...') which is transparent about not mutating data, but it does not define what 'active' means, whether the caller must be a member, or any other behavioral traits. The core action is clear, but meaningful details are absent.

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, well-structured sentence that states the action and scope with no filler words. It is appropriately sized for the tool's simplicity and front-loads the core purpose.

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?

While the tool is simple with one parameter and an output schema (so return values need not be described), the description leaves gaps around the 'topic' parameter format and the definition of 'active.' It is minimally sufficient for a basic list operation but could be more complete with explicit parameter semantics.

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 one required string parameter 'topic' with zero description coverage. The description repeats 'in a topic' but does not clarify whether the value should be a topic ID, name, or other identifier. No additional meaning is added beyond the parameter name itself.

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 uses the specific verb 'List' with resource 'topic members,' clearly distinguishing from siblings like list_topics (which lists topics) and create_topic/join_topic/leave_topic. It also adds the modifier 'active' to specify the scope of members, making the purpose precise.

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 provides no guidance on when to use this tool versus alternatives such as list_topics or read_messages. It lacks any mention of prerequisites, exclusions, or a context where this tool is preferred, leaving the agent to infer from sibling names alone.

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