get_connpass_user_group_list

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It provides no details about read-only guarantees, authentication needs, response format, or any side effects, adding no context beyond the tool's name.

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, waste-free sentence that clearly names the resource and action. It is appropriately compact for a simple tool with one parameter.

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?

The absence of an output schema and annotations means the description should clarify what 'group information' includes and how the tool behaves. It does not specify response structure, limitations, or how this differs from sibling tools, leaving an agent with insufficient context to confidently invoke it.

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 fully documents the 'nickname' parameter with a clear description ('Connpass user ID/nickname'), and schema coverage is 100%. The tool description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 a specific verb 'Fetch' and resource 'Connpass user group information', clearly indicating the action. However, it does not distinguish from sibling tools like get_connpass_user_list or get_connpass_user_events, leaving ambiguity about the exact scope of 'group information'.

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 about when to use this tool over alternatives. The description only states the basic action without referencing sibling tools, prerequisites, or contextual triggers, leaving the agent without direction on selection.

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