faceit_searchClans

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

No annotations, but description includes the HTTP method (GET) implying read-only. However, it does not explicitly state non-modification, auth requirements, or rate limits. Adds endpoint and parameter details.

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?

Concise and well-structured: intro, use case, endpoint, parameter list, return. Every sentence adds value with no redundancy.

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?

Lacks detail on return format ('List of hub' is vague), pagination behavior, and error handling. Without output schema, more explanation on clan records structure would improve completeness.

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%, but the description lists parameters with types, constraints (min/max), and brief explanations (e.g., 'The name of a clan on FACEIT'), which adds meaning 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 explicitly states it searches for clans, specifies using a clan name, and returns clan records with IDs. It distinguishes from siblings like searchPlayers or searchTournaments by focusing on clans.

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?

Clear guidance to use when only a clan name is available. No explicit exclusions or alternatives, but the context is well-defined.

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