PIX4Dmatic MCP

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 mentions running a job but doesn't clarify if this is a read-only or mutating operation, what permissions are needed, potential side effects, or how it interacts with the PIX4Dmatic environment. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that efficiently states the tool's action and context. It's front-loaded with the core purpose and avoids unnecessary words, though it could be more informative without sacrificing conciseness.

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 implied by a 'job object' with nested properties, no annotations, and 0% schema coverage, the description is inadequate. While an output schema exists, the description doesn't address key aspects like what the job does, how it affects the session/project, or error handling, making it incomplete for effective use.

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%, and the description doesn't add any meaning beyond the schema. It mentions 'job object' but doesn't explain its structure, required fields, or how it relates to the 'job' parameter. With 1 parameter and no schema descriptions, the description fails to compensate for the lack of documentation.

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 the action ('run a job object') and target ('against the current PIX4Dmatic session or an existing project_path'), which clarifies the basic purpose. However, it doesn't distinguish this tool from its sibling 'pix4d_run_job' or explain what a 'job object' entails, leaving the purpose somewhat vague.

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 is provided on when to use this tool versus alternatives like 'pix4d_run_job' or 'pix4d_start_processing'. The mention of 'current session' or 'existing project_path' implies some context but doesn't specify prerequisites, exclusions, or comparative use cases.

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