PIX4Dmatic MCP

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 states 'load and run' which implies a write/mutation operation, but doesn't disclose behavioral traits such as whether it's destructive, requires specific permissions, has side effects (e.g., starting processing), or handles errors. This leaves significant gaps for a tool that likely performs critical actions.

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 very concise ('Load and run a JSON job file.'), which is efficient and front-loaded. However, it's arguably too brief given the tool's likely complexity, missing necessary details that could earn its place in a single sentence.

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 likely involves job execution (a complex operation), no annotations, 0% schema coverage, but with an output schema present, the description is incomplete. It doesn't explain what 'run' entails, potential impacts, or how it integrates with other tools, making it inadequate for safe and effective use despite the output schema.

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%, with one parameter 'job_path' undocumented in the schema. The description adds no meaning beyond the schema—it doesn't explain what 'job_path' represents (e.g., file path format, expected content of the JSON job file). This fails to compensate for the low coverage, leaving the parameter poorly understood.

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 'Load and run a JSON job file' clearly states the action (load and run) and resource (JSON job file), but it's somewhat vague about what 'run' entails in this context (e.g., processing, execution). It distinguishes from siblings like 'pix4d_check_outputs' or 'pix4d_get_status' by focusing on job execution, but doesn't explicitly differentiate from 'pix4d_run_job_object' which likely handles similar functionality.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a job file prepared), when not to use it, or how it relates to siblings like 'pix4d_run_job_object' or 'pix4d_start_processing'. The description implies usage for job execution but offers no contextual advice.

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