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 context about the contents (the seven demos) and their reproducibility, but does not disclose additional behavioral traits such as return format or pagination. Since annotations cover the main risks, a score of 3 is appropriate.

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 highly concise, two sentences that immediately state the action and list the exact demos. It avoids fluff and front-loads the most critical information (what the tool does and when to use 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?

For a zero-parameter discovery tool, the description is complete. It names all seven demos, explains how they relate to run_* tools, and provides usage guidance. Even without an output schema, the description clearly tells the user what they will get (a list of the seven named demos), so the tool is fully understandable.

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?

With zero parameters, the tool has no parameter information to clarify, and the baseline for parameter semantics is 4. The description focuses on the tool's purpose rather than parameters, which is sufficient given there are none.

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 states a specific verb ('List') and resource ('the seven DRS demos') with explicit names, making the tool's function unambiguous. It clearly distinguishes itself from sibling tools like describe_demo and run_* tools by focusing on discovery/listing rather than describing or executing.

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 description explicitly says 'Use this to discover what's available before calling describe_demo or a run_* tool,' providing direct guidance on when to use it and naming the alternative tools it should precede. This is clear and actionable.

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