list_scenarios

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

With no annotations, the description carries the full burden. The verb 'List' strongly implies a read-only operation and the description notes these are built-in presets, but it does not disclose whether the list is exhaustive, whether it can be filtered, or whether any side effects or permissions are involved.

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 compact, front-loaded sentence with no filler. Every element earns its place: the verb, the resource, the scope qualifier, and the returned fields.

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-parameter listing tool with no output schema, the description adequately covers purpose and return content. It stops just short of stating explicitly that it only lists and never executes scenarios, though that is strongly implied by the wording and sibling names.

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?

There are zero parameters, so the input schema requires no further explanation. The description instead adds value by specifying what each returned preset includes, which is the relevant semantic content for this tool.

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 names a specific verb ('List') and a resource ('built-in end-to-end scenario presets'), and even enumerates the returned fields. This clearly differentiates it from scenario execution tools like plan_scenario and execute_scenario.

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 implies this is the discovery step before choosing or running a scenario, but it does not explicitly say 'use this before plan_scenario/execute_scenario' or mention any alternatives. For a simple listing tool, this implied usage is adequate but not fully explicit.

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