PIX4Dmatic MCP

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a write operation ('Collect... into a diagnostics directory') but doesn't disclose permissions, side effects, or output format. The existence of an output schema helps, but the description lacks details on what 'collect' entails beyond the basic action.

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, efficient sentence that front-loads the core action and resources. Every word contributes directly to explaining the tool's function without unnecessary elaboration.

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 tool's moderate complexity (collecting multiple resources) and no annotations, the description is incomplete—it lacks behavioral details and parameter guidance. However, the presence of an output schema mitigates some gaps by likely defining return values, preventing a lower score.

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, but it adds no parameter-specific information. It mentions 'diagnostics directory' which loosely relates to 'output_dir', but doesn't explain 'project_dir' or parameter interactions. With 2 parameters and no schema descriptions, the baseline is low, but the description provides minimal context, warranting a score of 3.

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 the action ('Collect') and the resources involved ('screenshot, recent logs, and status into a diagnostics directory'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'pix4d_screenshot' or 'pix4d_read_latest_logs', which handle similar resources individually.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing, or comparisons to siblings like 'pix4d_check_outputs' or 'pix4d_get_status', leaving usage context unclear.

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