huddo_members

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

No annotations exist, so the description carries the full burden. It does disclose the return shape (presence values online|busy|offline, identity_type, role, note), which is genuinely useful given there is no output schema, but it says nothing about auth requirements, rate limits, or whether room selection mutates default state (that only appears in the schema).

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 dense sentence with the action front-loaded, followed by an inline output-format spec. Every token is doing work, though the '· note' fragment is terse to the point of ambiguity.

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?

For a read-only two-param tool with no annotations and no output schema, the description covers the action and sketches the return format. It omits pagination/limits behavior and any statement that it is non-mutating, leaving gaps an agent might need.

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 description coverage is 100%, so both `as` and `room` are already documented with defaults in the schema. The description adds no parameter-level meaning beyond the baseline; 'members of a room' only echoes the `room` parameter.

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 the members of a room', which an agent can distinguish from siblings like huddo_list (rooms) or huddo_whoami (self). It does not explicitly name a sibling it is not, so it stops short of 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?

There is no guidance on when to use this versus huddo_list, huddo_whoami, or huddo_status, and no mention of prerequisites. Usage is only implied by the verb 'List'.

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