get_games

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond that: 'Free (0 credits)' informs the agent of cost implications, which is useful operational knowledge not present in 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?

The description is a single concise sentence plus a cost note. Every word earns its place, no redundancy, and the most important information (what it gets and its purpose) is front-loaded.

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 zero parameters, a clear purpose, an output schema available, and annotations covering safety, the description is complete. It also includes cost information, which is relevant for an agent deciding whether to use the tool. No further details are necessary.

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?

The tool has zero parameters, and the input schema is empty, so there are no parameter semantics to explain. The baseline for zero parameters is 4, and the description appropriately focuses on the tool's purpose and cost rather than nonexistent parameters.

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's function: 'Get available game names for Twitch discovery filters.' It uses a specific verb ('Get') and resource ('game names'), and the mention of 'Twitch discovery filters' distinguishes it from sibling tools like get_locations and get_languages.

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 phrase 'for Twitch discovery filters' provides clear context for when to use this tool, implying it is for populating game filter options. It does not explicitly state when not to use it, but its purpose is self-evident given the sibling tools are all discovery filters.

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