list_group_members

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the Qiita Team restriction but doesn't describe pagination behavior (implied by parameters), rate limits, authentication requirements, error conditions, or return format. For a list operation with pagination parameters, this leaves significant 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, efficient sentence that gets straight to the point. The parenthetical '(Qiita Team only)' is appropriately placed as a constraint modifier. No wasted words or unnecessary elaboration.

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 list operation with pagination parameters and no output schema, the description is insufficient. It doesn't explain what the return format looks like (array of members? what fields?), how pagination works with the page/per_page parameters, or any error scenarios. The Qiita Team restriction is helpful but doesn't compensate for other missing context.

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 the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 action ('List members') and target resource ('of a group'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_group_member' (singular) or 'list_groups', which could cause confusion about scope.

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 some context with '(Qiita Team only)', indicating a platform restriction, but doesn't explicitly state when to use this tool versus alternatives like 'get_group_member' or 'list_groups'. No guidance on prerequisites or exclusions is provided beyond the platform limitation.

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