PIX4Dmatic MCP

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

No annotations are provided, so the description carries full burden. It mentions 'clicking' which suggests a UI automation behavior, but fails to disclose critical traits: whether this is a read-only or destructive operation, authentication needs, error handling, rate limits, or what 'processing' entails. The description is insufficient for a tool with potential side effects.

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, straightforward sentence that's front-loaded with the core action. There's no wasted verbiage, though it could be more informative. It's appropriately sized for a simple tool but lacks depth.

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 2 parameters with 0% schema coverage, no annotations, and an output schema (which helps but isn't described), the description is incomplete. It doesn't explain what 'processing' is, the tool's behavior, or parameter usage. For a UI automation tool with potential complexity, this leaves significant gaps for an agent to operate effectively.

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 two undocumented parameters. It provides no information about 'selectors' or 'timeout_sec'—what they mean, how they're used, or their impact. The description adds zero semantic value beyond the schema, leaving parameters completely unexplained.

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 'Start processing by clicking the first matching processing control' which provides a verb ('start processing') and action ('clicking'), but it's vague about what 'processing' entails and doesn't distinguish from siblings like 'pix4d_run_job' or 'pix4d_run_job_object'. It's not tautological but lacks specificity about the resource or domain context.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for starting processing via UI interaction, but it doesn't clarify prerequisites, when to choose this over programmatic job execution tools, or any exclusions. Usage is only loosely implied by the action described.

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