Search clans

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

With no annotations provided, the description must disclose key behavioral traits. It simply says 'search', implying a read operation, but does not mention any destructive potential, authentication needs, rate limits, or what happens with no filters. The schema's limit parameter is not highlighted in the description.

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 short sentence, which is concise but may be too sparse. It is front-loaded with the main action, but lacks structure for additional details. It is not verbose, but could be expanded without harming conciseness.

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 the tool has no output schema, no annotations, low schema coverage, and multiple parameters, the description is severely incomplete. It does not explain the return format, sorting, pagination, or any behavioral aspects, leaving the agent with insufficient information to use the tool correctly.

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 0%, meaning the description adds no meaning to the parameters (name, limit, minMembers). The description does not compensate by explaining how these parameters affect the search, so the agent gets no extra help beyond the raw 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 clearly states the verb 'Search' and the resource 'clans', and mentions the method 'by name and/or filters'. It distinguishes from sibling tools like 'coc_search_clans' which belong to a different game. However, it does not elaborate on what specific filters are available, relying on the schema for details.

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 given on when to use this tool versus alternatives such as 'coc_search_clans' or specific lookup tools like 'cr_get_clan'. The description lacks any context about prerequisites or exclusions.

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