oc_run_finish

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

The description's 'Finish' aligns with annotations showing destructiveHint=true. It does not add additional behavioral context beyond what annotations provide, such as side effects or required run state.

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 sentence that conveys the essential information without any unnecessary words. It is front-loaded and efficient.

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 simple finish action with no output schema, the description adequately covers the purpose and allowed statuses. It lacks mention of error conditions or prerequisites, but the completeness is high given the tool's simplicity.

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?

All parameters are described in the input schema with 100% coverage. The description provides no extra meaning beyond the schema definitions, so baseline score of 3 applies.

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 clearly specifies the action (finish), the resource (OpenChrome run ledger), and the allowed statuses. However, it doesn't explicitly differentiate from sibling tools like oc_task_finish, but the resource name is distinct enough.

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 the tool is used when a run needs to be finished with a specific terminal or ongoing status. It does not mention when not to use it or suggest alternatives like checking run status first.

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