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

No annotations are provided, so the description carries the full behavioral burden and delivers none of it. It does not state result limits, pagination, whether the search is exact or prefix-based, or what the response contains. Two words cannot cover the behavior of a search endpoint.

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?

At two words the description is certainly not bloated, but its brevity is under-specification rather than disciplined conciseness. There is no wasted sentence because there is essentially no content.

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 search tool with two required parameters and no output schema, the description should explain the result shape, ordering, or result caps, and should route between this tool and clans_search_ndjson. None of that is present, leaving an agent without enough to call it confidently in ambiguous cases.

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%, and the schema itself documents 'q' as a search prefix and 'region' with an enum of eu/na/asia. The description adds nothing beyond that, so the baseline of 3 for fully documented parameters applies.

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 pairs a verb ('Search') with a resource ('clans'), so the basic operation is identifiable. However, it does nothing to distinguish itself from the sibling clans_search_ndjson, which appears to be the same search in streaming form, nor from clans_by_tag or clans_top. It is the minimum viable statement of purpose.

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 search versus clans_search_ndjson, when to look up a clan by tag instead, or what the two required inputs (a prefix and a region) imply about intended usage. The agent must infer everything from the schema alone.

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