gate_set_baseline

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

No annotations are provided, so the description carries the full burden. It does disclose one behavioral trait beyond the schema – the new baseline is merged over rather than replacing the old – but it omits whether the operation is reversible, what permissions it needs, and what happens to existing baseline data not present in the run.

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?

A single short sentence with no padding, so nothing is wasted. But the terseness borders on cryptic and the parenthetical merge note is buried rather than front-loaded as a key semantic.

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?

For a mutation tool with no annotations, no output schema, and an undocumented parameter, the description is far too thin. An agent cannot determine prerequisites, side effects, or expected outcome from this definition alone.

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% for the single run_id parameter, so the description must compensate. 'A run's rows' implies run_id selects the source run, but it gives no format, identifier scheme, or constraint on which run is valid, leaving the parameter largely unexplained.

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 conveys that a run's rows are promoted to become the baseline and that the old baseline is merged over, which is a specific state-changing action on a named resource. However, it relies on undefined domain jargon ('rows', 'baseline', 'merged over') and gives no hint of how this differs from siblings like gate_run, gate_verdict, or gate_approve.

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?

There is no when-to-use guidance, no prerequisite (e.g. whether the run must be completed or approved first), and no mention of alternatives despite a large set of gate_* siblings. The agent must infer the trigger condition entirely.

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