rush_flaky

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It reveals two modes and one gating flag, but says nothing about side effects, where the report is imported to, required permissions, transformations applied, or whether the operation is read-only or mutating.

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 single sentence is efficient and front-loaded, with no filler words. That conciseness comes at the cost of missing essential detail for a nine-parameter tool, making it under-specified rather than appropriately concise.

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?

Given nine parameters, no annotations, and only a one-line description, the agent lacks enough context to invoke this tool correctly with confidence. The output schema may describe return values, but invocation semantics, mode selection, and the meaning of most flags are missing.

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 0%, so the description must compensate for all nine parameters, but it only lightly touches allow_slow and the JUnit report path. The remaining parameters such as allow_build, report_path, allow_network, and allow_artifact_write receive no semantic explanation 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?

The description names two actions — importing a local JUnit report and running duplicate test analysis — so it is not a tautology and is somewhat concrete. However, 'duplicate test analysis' is unexplained, and the tool name 'rush_flaky' suggests flaky-test detection but the description never mentions flakiness, forcing the agent to infer intent.

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 conditional 'under --allow-slow' provides a meaningful usage hint, and 'import a local JUnit report' implies a common invocation scenario. There is no explicit guidance about when to prefer this over sibling tools, when not to use it, or what prerequisites apply.

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