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 launching or attaching to a process but doesn't describe what happens if the application is already running, whether this requires specific permissions, potential side effects (e.g., opening windows), or error handling. This is inadequate for a tool that interacts with external software.

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 directly states the tool's action without unnecessary words. It's front-loaded with the core purpose and appropriately sized for the complexity, making it easy to parse quickly.

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 launching/attaching to an external application, no annotations, and an output schema (which might cover return values), the description is incomplete. It lacks details on behavior, prerequisites, error cases, and how it integrates with sibling tools, making it insufficient for safe and effective use by an AI agent.

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?

The input schema has 1 parameter with 0% description coverage, and the tool description provides no information about the 'exe_path' parameter. Since there's only one parameter, the baseline is 4, but the description fails to add any meaning beyond the schema, such as explaining what 'exe_path' is for (e.g., custom executable location) or default behavior when null, so it's scored lower.

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 verb 'launch' and resource 'PIX4Dmatic' with the alternative action 'attach to existing process', making the purpose specific and understandable. However, it doesn't explicitly distinguish this from sibling tools like 'pix4d_focus' or 'pix4d_get_status', which might involve application state management, so it misses full sibling differentiation.

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 (e.g., whether PIX4Dmatic must be installed), when to prefer launching vs. attaching, or how it relates to siblings like 'pix4d_focus' for application control, 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.