list_examples

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so the safety profile is covered. The description adds only that the samples are Valve-authored demo scripts; it says nothing about result volume, ordering, or how the 'API used' field is presented beyond the output schema.

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?

One front-loaded sentence with no filler; the scope qualifier follows the core statement rather than burying it.

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?

An output schema exists, so return values need no prose, and the lone parameter is fully documented in the schema. The only real gap is the unstated relationship to get_example, which an agent would have to infer.

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 100% and the single 'game' parameter already documents its allowed values (cs2, deadlock) and default. The description adds no meaning about the filter, so baseline 3 applies.

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?

Specific verb plus resource ('List example scripts') with the source scope named ('Valve's cs_script_demo samples') and what's returned per item ('the API each one uses'). It does not distinguish itself from the sibling get_example, so an agent can't tell from this text alone why to list rather than fetch one.

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 listing purpose implies a discovery-then-fetch workflow, but the description never says to call get_example afterwards or when this tool is preferable to it. No exclusions, prerequisites, or coverage statement (whether the list is complete or paginated).

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