Get clan member list

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to mention whether the operation is read-only (it likely is), any authentication requirements, rate limits, or what happens if the clan tag is invalid. The description is silent on all behavioral aspects.

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 very short (5 words), which is concise, but it sacrifices necessary detail. It is essentially a noun phrase with no verb, lacking structure. While brevity is valued, it does not earn its place because it omits critical context.

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 no output schema, the description should explain what the member roster contains (e.g., player names, roles, clan castle status). It only says 'member roster', which is vague. The single parameter is not described. For a low-complexity tool, the description is incomplete.

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 input schema has 0% description coverage for the single parameter 'tag'. The description does not mention the parameter at all, leaving the agent to infer that a clan identifier is needed but without specifying format (e.g., must start with '#') or origin. The description adds no semantic value 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 'Member roster for a clan' clearly indicates that the tool returns a list of members for a given clan. It distinguishes the tool from siblings like coc_get_clan (clan info) and coc_get_player (player info) by specifying 'member roster', though it does not explicitly name alternatives.

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 no guidance on when to use this tool versus alternatives. It does not specify prerequisites, such as requiring a clan tag, nor does it mention that coc_search_clans might be used to find the tag first.

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