athena_antibody_execute_regressions

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 does reveal that execution happens in a 'restricted repository-owned subprocess' and that arbitrary shell/command refs are rejected, which is valuable safety context. However, it omits side effects, recording behavior (despite the record_outcome parameter), and return values, leaving significant gaps.

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 a single, tightly-worded sentence that leads with the primary action and quickly covers key constraints. Every phrase earns its place, with no redundancy or vague filler.

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?

Despite a clear purpose, the description omits details on all parameters, expected output, and side effects. With no output schema and no annotations, these gaps prevent an agent from understanding the full invocation contract.

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%, and the description does not explain any parameter meanings. It only implicitly associates antibody_id with the witnesses, but fails to describe actor, max_refs, timeout_s, or record_outcome. This is insufficient for an agent to invoke the tool correctly.

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 verb ('Execute') with a clear resource ('stored failure-antibody unittest witnesses') and adds environmental context ('in a restricted repository-owned subprocess') plus a constraint ('no arbitrary shell/command refs are accepted'). This clearly differentiates it from related sibling tools like athena_antibody_evolve or athena_antibody_select.

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 does not state when to use this tool versus alternatives or provide usage context beyond its core function. The note that no arbitrary shell/command refs are accepted is a limitation, but it does not offer explicit guidance on when to choose this tool or when to avoid it.

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