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

Annotations already establish readOnlyHint=true, openWorldHint=false and non-destructive, so safety disclosure is handled. The description adds real value beyond that: the result set is fixed at five items and is fabricated demo data, and the entries carry evidence ids — details the annotations cannot convey, especially with no 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?

A single sentence plus a short qualifier, front-loaded with the main clause. Every clause carries information: count, domain, consumer tool, included field, and data provenance.

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 no-argument read-only list with full annotation coverage, the description supplies the essentials: what comes back, how many, and that the data is synthetic. With no output schema it could sketch the return shape slightly more (names plus ids), but the key field is already named.

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?

Zero parameters, so there is nothing to disambiguate and the baseline applies. The description correctly omits any parameter discussion rather than inventing one.

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 (Lists) plus resource (the five sample scenarios) and an explicit scope limitation: the ones run_check accepts. Naming run_check ties it to a sibling tool the agent already has, so its role is unambiguous.

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 'that run_check accepts' plus 'with their evidence ids' makes the intended use clear: call this to obtain valid scenario inputs for run_check. It stops short of explicitly saying when not to call it (e.g., in non-demo contexts), but the 'Demo data only' note covers that implicitly.

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