faceit_getQueueById

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

No annotations are provided, so the description must carry the burden. It states 'Retrieve details,' which implies a read operation, but does not explicitly confirm no side effects or required permissions. The description is adequate but not fully transparent about behavioral traits.

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 concise with a few sentences, including the endpoint and parameter list. It is front-loaded with the purpose. However, the endpoint and parameter details could be considered redundant given the schema, slightly reducing efficiency.

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?

The tool has 2 required params and no output schema. The description explains what the tool does and when to use it, but the return value is only described as 'Queue' with no detail. For a simple retrieval tool, it is adequate but lacks output format specifics.

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 coverage is 0%, so the description should compensate. It lists parameters with type and path location, but adds little beyond the schema. It restates game_id and queue_id without explaining their meaning or constraints, providing minimal added value.

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 tool retrieves details of a queue on FACEIT, and mentions configuration and current state. It specifies using when queue_id is known, which distinguishes it from sibling tools like getQueueBans or getQueuesByEntityFilters.

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 explicitly states when to use the tool ('Use when you already have a queue_id and want its configuration and current state'), providing clear context. It doesn't list alternatives or exclusions, but the context is sufficient for most scenarios.

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