faceit_getQueuesByRegion

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

No annotations are provided, so the description carries full burden. It describes the endpoint, parameter types, and return type ('Queues list'). It does not mention permissions or rate limits, but for a read-only list operation, it is adequately transparent. Could note pagination behavior implicitly.

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 succinct with a brief intro, a usage note, and a structured parameter list. Every sentence is functional and avoids redundancy. Front-loaded with purpose.

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 list endpoint with 4 simple parameters and no output schema, the description covers purpose, usage, parameters, and return. Lacks detail on the structure of the queues list, but the return type is mentioned. Sibling differentiation adds 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?

Despite 0% schema description coverage, the description fully documents all four parameters: location (path vs query), constraints (min/max, required/optional), and defaults. This adds significant value beyond the bare 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 queues by region' and explains it lists queues available in a specific region (e.g., EU, NA). It distinguishes from sibling 'getQueuesByEntityFilters' by specifying when to use that alternative.

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?

Explicitly says when to use this tool ('Use to list queues available in a specific region') and when not to ('Pick getQueuesByEntityFilters instead when filtering by non-region entities'), providing clear decision criteria.

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