wb_native_convert

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a write operation (conversion producing CR2W output) but never states whether existing output files are overwritten, what permissions or CLI path are required, how long conversion takes, or what a successful vs failed run reports. "Verified CLI" is asserted without explaining what verification means.

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?

Two short sentences with the action front-loaded and the default-mode caveat at the end; no filler. It is arguably under-written rather than over-written, but structurally clean.

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 tool with five undocumented parameters, no annotations, and no output schema, the description is too thin: the agent cannot tell what gets written where, whether prior output is destroyed, or how failures surface. The preview/execute distinction is the only operational detail provided.

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% across five parameters, and the description only clarifies 'run' (default false). It says nothing about the format or expected value of native_json, what output path semantics apply (file vs directory, overwrite behavior), what the cli parameter overrides, or what the timeout unit/default is.

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 verb and resource: converting WolvenKit JSON intermediates to CR2W, with a preview-vs-execute mode. It does not explicitly differentiate itself from close siblings such as wb_native_import, wb_native_json, or wb_native_preflight, so an agent must infer the boundary.

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?

"Preview or execute" plus "run=false by default" implies a safe dry-run first, which is useful implicit guidance. However, it never says when to choose this tool over wb_native_import or wb_native_preflight, nor what prerequisites the prepared JSON intermediates must satisfy.

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