colmap_to_ue

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

No annotations are provided, so the description carries the full burden. It does disclose output format (.csv or .json), the units of the emitted values, and the meaning of scale, but says nothing about whether existing output files are overwritten, whether the source directory is modified, or what happens on parse failure.

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 dense sentences, front-loaded with the conversion and output contents before the scale semantics and the downstream import hint. Every clause carries information; no filler.

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?

With no output schema and no annotations, the description does well on the transformation and result shape, but leaves two of three parameters undocumented and omits error/overwrite behavior. Adequate but with clear gaps for a 3-parameter file-writing 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%, so the description must compensate. It explains scale well (UE centimetres per COLMAP unit), but output and sparse_txt_dir are only inferable from context, with no format/path expectations stated for either.

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?

States a precise verb+resource: converting COLMAP cameras.txt + images.txt into Unreal camera keys, and enumerates the output fields (location in cm, pitch/yaw/roll, FOV). This is clearly distinct from the sibling colmap_solve, which only produces the COLMAP reconstruction this tool consumes.

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?

Usage is implied by the pipeline framing (convert COLMAP output, then import with unreal/import_camera_csv.py), but there is no explicit when-to-use, prerequisites, or statement of when not to use it.

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