list_mesh_members

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

With no annotations, the description carries the full burden, and it does disclose one meaningful trait: the underlying roster is 'gated on membership,' so a caller knows authorization is required. It says nothing about pagination, result size, error behavior, or whether invitations/join requests can be absent. Useful but incomplete for an annotation-free tool.

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 first sentence is well-formed and front-loaded, but the entire second paragraph is an engineering changelog (author, date, report number, endpoint archaeology) that carries zero selection or invocation value for an agent. Roughly half the description is noise.

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?

An output schema exists, so return values need not be restated. For a read-only, single-optional-parameter list tool with a disclosed membership gate and a documented default, the agent has enough to call it correctly. Only the absence of any sibling routing keeps it from a 5.

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 0% and the single parameter is documented only as anyOf string/null with default null. The description compensates by explaining that omission resolves to the active mesh, giving the null default real meaning. That is a genuine addition over the schema, though no format or ID-source detail is offered.

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 opening sentence names the resource (mesh members) and enumerates what comes back: members with roles, humans vs AI, pending invitations and join requests. That is far more specific than a tautology and implicitly separates it from list_channel_members. It stops short of an explicit sibling contrast, so a 4 rather than a 5.

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?

'Defaults to the active mesh' tells the agent what happens when mesh_id is omitted, which is genuine usage context. However, there is no statement of when to reach for this over list_channel_members, list_my_meshes, or whoami, and no exclusions. Usage is implied rather than guided.

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