bourne_execution_reconcile

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

Annotations already communicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds useful behavioral constraints like targeting exactly one execution and never resubmitting, but it does not explain what 'reconcile' actually does, what side effects may occur, or whether permissions or prerequisites are needed.

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 filler. Every word contributes: the action, the scope, the ownership constraint, and the critical 'never resubmit' warning.

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?

Although the tool has only one parameter and an output schema, the description leaves the meaning of 'reconcile' vague and gives no trigger conditions or behavioral detail beyond 'never resubmit.' An agent can avoid resubmission but cannot reliably know when or how to invoke this tool.

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 never mentions the 'reference' parameter. The name implies it is an identifier, but the description does not connect it to the execution being reconciled or explain what form it should take.

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 states a specific action ('Reconnect and reconcile') and a precise resource ('one exact Bourne-owned remote execution'), then adds a clear negative constraint ('never resubmit'). This distinguishes it from resubmission-style siblings and makes the tool's scope obvious.

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 usage context is implied: use this when reconnecting a Bourne-owned execution to reconcile its state. However, there is no explicit when-to-use guidance, no mention of when not to use it, and no naming of alternative tools such as bourne_execution_get or bourne_execution_wait.

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