wb_native_preflight

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

With no annotations supplied, the description carries the full disclosure burden. It does not say whether probing spawns an external process, whether it is read-only or writes anything, what happens if the CLI is missing, or what the result looks like (boolean, log, capability matrix) — all critical for a tool whose name suggests running an external binary.

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 front-loaded sentence with no filler; the subject and action come first. It is under-specified rather than verbose, so conciseness itself is not the problem.

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?

No output schema, no annotations, and 0% parameter documentation leave the agent guessing about both inputs and return values for a tool that presumably shells out to an external CLI. For this level of complexity the description is too thin to call the tool correctly on the first try.

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 both parameters. The description's mention of 'WolvenKit CLI/cp77tools' loosely hints that the 'cli' parameter selects which backend to probe, but it never explains accepted values, defaults, or what 'timeout' controls (probe duration? process kill threshold?). The meaning added over the bare schema is minimal.

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 a verb ('Probe') and a target ('WolvenKit CLI/cp77tools') plus the capability being checked ('convert deserialize JSON-to-CR2W'). However, the phrasing is compressed to the point of ambiguity, and it does nothing to separate itself from adjacent siblings such as wb_native_convert, wb_native_verify, or wb_worker_preflight, so an agent cannot tell whether this performs a conversion or only checks that conversion is possible.

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 guidance on when to call this versus wb_native_convert, wb_native_verify, or wb_build_backends, and no mention of prerequisites or ordering (e.g., run before attempting a native import). The word 'preflight' implies a pre-check role, but that is inference rather than stated guidance.

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