faceit_getChampionshipResults

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits like read-only nature, idempotency, rate limits, or authorization requirements. Only minimal operational details are given.

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 well-structured: purpose sentence, usage guideline, endpoint, then parameter list. Each sentence serves a purpose with no waste. Front-loaded with key information.

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?

With no output schema, the description only says 'Returns: Championship results' which is vague. It does not mention pagination defaults (though schema shows default 20 for limit) or structure of results. Adequate for a simple list but could provide more context for a self-contained description.

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% (no descriptions in schema), but the description adds comprehensive parameter details: type, location (path/query), required, min/max, defaults, and purpose for each parameter. This greatly enhances understanding 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 clearly states 'Retrieve all results of a championship' with a specific verb and resource. It distinguishes from sibling tool faceit_getChampionshipMatches by noting when to use each: final results vs. live/upcoming matches.

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 'Use when you only care about the final results' and provides an alternative ('For live/upcoming match details use getChampionshipMatches'), giving clear context and exclusion.

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