Run Behavioral Verification

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly discloses the black-box nature, treats both executables as opaque, and details the comparison modes. However, it does not describe the return value or status semantics, which is a gap given the lack of an output schema.

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 four sentences long, front-loaded with the main purpose, and every sentence adds distinct value. It avoids repetition of schema details and is well-structured for quick parsing.

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?

The tool has 5 parameters and a nested test_cases structure, with no output schema or annotations. The description covers mechanism and constraints but omits what the tool returns after comparison (e.g., pass/fail per test case, exit codes, or a report reference), which is essential for an agent to act on results. This is a notable 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 80%, so the baseline is 3. The description adds value by explaining the comparison_mode enum values in detail (exact, fuzzy, semantic) and clarifying that test_cases are fed identically to both commands, which goes beyond the schema's minimal descriptions.

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 clearly states the tool compares the reimplementation's behavior against the original software using black-box testing, specifying the verb and resources. It also distinguishes this from sibling tools like cleanroom_verify_report, which likely handles reporting, and cleanroom_impl_run_tests, which likely runs tests.

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 provides clear context on execution method (feeds identical inputs, compares outputs, no source code access), making it obvious when this tool is appropriate for behavioral verification. It does not explicitly name alternative tools or exclusions beyond stating it does not access source code, so it misses the full 'when-not' guidance.

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