List PoC Recording Scenarios

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

No annotations exist, so the description carries the full burden. It implies a read-only discovery operation and discloses the 'configured roots' fallback when no directory is given, which is useful behavioral context, but it says nothing about traversal depth, result ordering, or error behavior for invalid roots.

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 front-loaded sentence with no filler; the glob and the scope qualifier are efficiently packed. It is lean but arguably under-informative rather than padded.

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?

With no output schema, the description should describe what a discovered scenario looks like (name, path, metadata), and it does not. Both parameters are covered by the schema, so the core invocation is clear, but the return shape is a real gap.

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 description coverage is 100%, so both root and query are already documented in the schema, establishing a baseline of 3. The 'under a directory or configured roots' phrase loosely reinforces the root parameter's default behavior, but adds no syntax or format detail, and the query filter is not mentioned at all.

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 verb (Discover) and resource (`*.scenario.json` recording definitions), and the file glob makes the target unambiguous. It does not explicitly contrast itself with the sibling list-recordings, so an agent could still conflate scenario definitions with recordings.

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?

No when-to-use guidance is given, and no alternative is named. An agent is left to infer that this is the discovery step preceding run-scenario or record-poc rather than a differently-scoped listing sibling like list-recordings.

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