get_members

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

Since annotation is absent, the description must convey behavioral traits. It does disclose the default plain-text output and the option to request JSON, which goes beyond the schema. However, it omits details like rate limits, error handling, or whether the operation is read-only, leaving some gaps.

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 sentence containing only essential information: what the tool does, what it returns, and the format option. No redundancy or unnecessary words.

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's simplicity (2 params, no output schema), the description covers the key aspects: it lists the output fields and mentions the format parameter. It lacks details on pagination or error conditions, but for a straightforward listing tool, it is largely sufficient.

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 coverage is 100%, so the schema already describes both parameters. The description adds value by implying the default format (text) via 'by default', which is not in the schema. For session_id, no additional meaning is added beyond the schema.

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 clearly states the verb 'lists' and the resource 'members in a session', specifying the returned fields (platformId, name, role). This distinguishes it from sibling tools like get_messages or get_member_activity, which focus on different entities or activities.

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 alternatives. It does not mention scenarios where get_member_activity or other sibling tools might be more appropriate, nor does it specify any prerequisites or context for usage.

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