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

The description states that the tool changes run state ('Move a run back to open', 'abandon it'), but the annotations declare readOnlyHint=true, meaning the tool should not modify the environment. This is a direct contradiction, so the behavioral transparency score must be 1.

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 two sentences with no filler. The primary operations and their use cases are front-loaded, and the important signed-off refusal constraint is stated compactly. Every sentence earns its place.

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 four-parameter tool with a fully described schema and no output schema, the description covers the essential behavioral constraints: what state transitions are possible, when each is appropriate, and that signed-off runs are refused. It is slightly incomplete on edge-case behavior such as already-open or already-abandoned runs, but the core context is present.

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 100%, so the schema already documents run, date, note, and status. The description adds a little context for what 'open' and 'abandoned' mean, but it does not add meaningful parameter-level semantics beyond the schema. Baseline 3 is appropriate.

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 the exact operations ('Move a run back to open', 'abandon it') and the target resource (a run), and it distinguishes this from sibling tools like run_sign_off by stating that a signed-off run is refused. The title and description align with a clear verb+resource structure.

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?

It gives explicit when-to-use guidance: reopen when a step must be answered again, abandon when the job did not happen. It also gives a when-not: signed-off runs are refused. However, it does not explicitly name an alternative tool such as run_sign_off for the normal close path, so it falls just short of full alternative routing.

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