faceit_getQueueBans

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

No annotations provided. Description only states it's a GET request returning a bans list, with no mention of authentication, rate limits, or side effects. Minimal behavioral insight.

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?

Description is structured with a clear intro, endpoint line, parameter list, and return info. Front-loaded with purpose. Slightly verbose with explicit endpoint, but overall efficient.

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?

Covers basics: purpose, parameters, return. Lacks details on authentication, error handling, pagination behavior, or what bans contain. Adequate but with gaps.

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 compensates by detailing each parameter's purpose, type, location (path/query), and constraints (min/max). Adds significant meaning beyond 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 'Retrieve queue bans on FACEIT' with specific verb and resource. It differentiates from siblings like faceit_getQueueById by focusing on bans.

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 implies usage ('Use to list...') but offers no explicit when-to-use vs alternatives or when-not-to-use. Siblings include many queue-related tools, so guidance is lacking.

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