photogrammetry_colmap_pose_matcher

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the primary action (validates, filters) but does not disclose whether the operation is read-only or mutating, what data is required, what the output format is, or any side effects or limitations. The price is mentioned, but not the operational behavior details.

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, well-structured sentence that front-loads the core purpose and includes the cost in parentheses without extra fluff. Every word earns its place; it is concise and readable.

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 complexity of photogrammetry and pose estimation, plus the absence of an output schemaaging or annotation coverage, the description is too minimal. It does not explain what fields the payload should contain, what output to expect, or any operational requirements (e.g., whether the input must come from COLMAP, how many images are needed). An agent would struggle to invoke this tool correctly with only this text.

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 100%, so the baseline is 3. The schema describes both parameters ('payload' as a JSON string and 'paymentSignature' for settlement). The tool description adds no additional meaning about how to construct or interpret the payload, so it does not improve upon the schema.

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 clearly states a specific verb ('Validates') and resource ('camera extrinsic poses and epipolar geometric constraints from multi-view image sets'), with a concrete outcome ('filtering false parallax feature correspondences'). It is distinct enough from the sibling list, especially other photogrammetry tools, though it does not explicitly name a sibling alternative, so it stops short of a 5.

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 description gives no guidance on when to use this tool versus alternatives. It does not mention any exclusion criteria, prerequisites (e.g., COLMAP output format), or when to prefer a sibling tool. Only the phrase 'from multi-view image sets' implies a use case, but that is insufficient guidance.

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