run_test_suite

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

With annotations already declaring readOnlyHint=false, openWorldHint=true, destructiveHint=false, the description adds real value: it discloses the return content (summary and failed assertions) and the side effect of junit_path writing a JUnit XML file. It does not mention that execution may hit external services or any permission/environment implications, so it stops short of 5.

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?

Two compact sentences, front-loaded with the core action and scope, then the filtering option and side-effect. Every clause carries information; only minor cost is the awkward line break splitting the sentence.

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?

An output schema exists, so return values need not be explained, though the description usefully mentions failures. However, with five parameters at zero schema documentation, two parameters (verbosity, environment) remain entirely opaque, leaving the definition incomplete for correct invocation.

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 coverage is 0%, so the description must carry parameter meaning. It explains path (recursive folder traversal), tags (selective filtering), and junit_path (report output), but leaves verbosity and environment completely undocumented in either schema or description.

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 and resource ('Run every scenario under a folder (recursively)') and its scope distinguishes it from the single-scenario sibling run_scenario. It does not name that sibling explicitly, but the folder-level scope makes the difference inferrable.

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 when to use it (bulk folder execution, optional tag filtering) but never states when to prefer run_scenario or validate_scenario instead, nor any preconditions. Usage is inferable rather than guided.

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