timps_flaky_test_hunter

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

No annotations are provided, so the description carries the full burden of disclosing side effects and behavior. It states the tool 'finds' and 'returns' results, which suggests read-only analysis, but it never explicitly says whether it writes to the repo, makes external calls, or only parses the supplied CI history. This lack of explicit safety/behavioral disclosure is a meaningful gap.

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 one sentence, concise, front-loaded with the main action, and has no redundant filler. It efficiently communicates the purpose and the nature of the returned result.

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 the low complexity of the tool, the description adequately covers what the agent needs to know: the purpose, input domain, and output shape. It lacks explicit behavioral/safety details, but those are already accounted for in behavioral transparency; for a simple analyze-and-return tool, the description is complete enough.

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 schema fully describes both parameters with 100% described coverage, so the baseline is 3. The description reinforces that CI history is the core input, but it adds no new parameter-level semantics beyond what the schema already states. More guidance on acceptable `ci_history` format or how `repo_path` would be used would improve this dimension.

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 uses a specific action ('Find non-deterministic tests') and identifies the source data ('CI run history') and output ('ranked list of flaky tests, suspected causes, and fix suggestions'). It is clear, but it does not distinguish itself from the closely named sibling timps_flaky_test_detective.

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 the tool: when the agent has CI run history and wants flaky-test analysis. However, it provides no explicit guidance about alternatives or when not to use it, which matters because the sibling list includes `timps_flaky_test_detective`, `timps_test_intelligence`, and similar analysis tools.

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