colmap_solve

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the COLMAP installation prerequisite and that the model is exported as TXT, but it omits critical behavioral details such as whether it writes files to the workspace, expected runtime, GPU requirements, overwrite behavior, and error modes.

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 wasted words. The purpose, prerequisite, and output format are packed efficiently, and every clause earns its place.

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?

Given the 0% schema coverage, no annotations, no output schema, and four parameters, the description is too sparse. It covers the high-level purpose and prerequisite but leaves parameter meanings, usage routing, and behavioral side effects largely unexplained, so an agent cannot invoke it confidently with correct arguments.

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 for all four parameters. It only indirectly clarifies image_dir as 'a frame folder' and gives no meaning for workspace, quality, or single_camera, leaving most parameter semantics undocumented.

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 ('Solve the camera'), resource ('from a frame folder'), and implementation ('with COLMAP'), plus an output format ('export the model as TXT'). It is clear what the tool does, but it does not explicitly differentiate itself from the sibling tool colmap_to_ue or other frame-processing siblings.

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 explicit guidance on when to use this tool versus alternatives, nor any when-not conditions. The only usage-adjacent information is the prerequisite that COLMAP must be installed, which is useful but does not constitute selection guidance.

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