List Counter-Strike matches

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the match categories and filter types, which is useful but not deeper behavioral traits like pagination or rate limits. No contradiction with annotations.

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?

Two sentences: the first front-loads the core purpose, the second lists filter options. No redundant or wasted words.

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?

Given the tool's complexity (6 optional params, output schema, annotations), the description is sufficient: it states what it does and the main filters. It doesn't mention defaults for kind/limit, but those are in the schema. Acceptable for a list tool.

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 high (83%), so baseline is 3. The description summarizes the filter parameters (team, event, date, limit) but adds little beyond the schema, except emphasizing 'exact team display name' and referencing event IDs from search_hltv_entities.

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 it lists Counter-Strike matches from HLTV.org, with a specific verb 'List' and resource. It enumerates filters (team, event, date range, limit) that distinguish it from sibling tools like get_hltv_match and search_hltv_entities.

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?

Provides clear context on the tool's scope (upcoming/live/finished matches) and filter options. However, it does not explicitly mention when to use this over get_hltv_match or how to obtain event IDs, though the schema references search_hltv_entities.

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