List ready-made scenarios

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

'Changes nothing' restates readOnlyHint=true rather than adding to it. The genuinely additive part is describing the return contents (names and what each scenario tests), which matters because there is no output schema, but it says nothing about list size, ordering, or pagination.

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 with the resource first, the consumer second, and a safety note last. No sentence is redundant in substance, though 'Changes nothing' is close to filler given the annotations.

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, read-only list tool with no output schema, the description covers what it returns and why an agent would call it. Minor gaps: no hint about how many scenarios come back or whether ordering is stable.

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 takes zero parameters, so there is no parameter semantics to document and the baseline applies. Nothing in the description misleads about inputs.

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?

States a specific resource (ready-made scenarios) and a specific payload (the name plus what each scenario tests). It also names the sibling that consumes the output, twin_load_scenario, so an agent can tell it apart from twin_status or twin_changes without opening any schema.

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?

By saying these are the scenarios 'twin_load_scenario can load by name', it makes the discovery-then-load workflow implicit and clear. It stops short of an explicit 'call this before loading' instruction or any exclusion, so it is strong context rather than a full when/when-not statement.

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