freeze_run_set

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

Annotations are all false (not read-only, not idempotent, not destructive), so they provide little safety context. The description adds the notion of 'freeze' implying immutability or persistence, but it does not disclose side effects, reversibility, or whether it modifies existing data. This is insufficient for a mutation-like tool with no safety hints.

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, front-loaded sentence with no wasted words, which is commendable. However, it is under-specified for a tool with a complex nested request schema. It is concise but not appropriately sized, leaving critical details unexplained.

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 having an output schema (which reduces the need to explain return values), the description is inadequate for the tool's complexity. It fails to define core concepts ('bounded cohort', 'corpus snapshot'), explain what 'freeze' entails, or clarify how to specify the cohort. The tool operates in a domain with many analytical siblings, but the description lacks enough context to guide correct invocation.

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 mentions no parameters or request structure. The single 'request' parameter is a complex oneOf with distinct member/run_id modes, but the description gives no clues about how to populate it. The phrases 'bounded cohort' and 'corpus snapshot' vaguely imply the request fields but do not add concrete parameter semantics.

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 ('Freeze') and resource ('a bounded cohort') with a scoping phrase ('against one corpus snapshot'). It clearly indicates the tool's function and differentiates it from siblings like 'compare_run_sets.' However, the terms 'bounded cohort' and 'corpus snapshot' are domain-specific and not elaborated, preventing a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or preferred scenarios. The sibling tools (e.g., 'compare_run_sets', 'plan_experiment') suggest related operations, but the description offers no differentiation or selection criteria.

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