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 of behavioral disclosure. It states the tool checks for existence of outputs, implying a read-only operation, but doesn't cover critical behaviors: whether it requires specific permissions, how it handles missing or partial outputs, if it returns structured data or simple booleans, or any performance or rate limit considerations. This is a significant gap for a tool with no annotation coverage.

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 purpose without unnecessary words. Every element ('check', 'expected PIX4Dmatic outputs', 'under a project directory') contributes directly to understanding the tool's function, with zero redundancy or fluff.

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 (2 parameters, no annotations, but with an output schema), the description is partially complete. It covers the basic action but lacks behavioral context (e.g., error handling, return format). The presence of an output schema reduces the need to describe return values in the description, but without annotations, more detail on operational constraints would improve completeness for safe agent 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%, so the description must compensate. It mentions 'project directory' and 'expected outputs', aligning with the two parameters ('project_dir' and 'expected'), but adds minimal semantics beyond the schema's titles. It doesn't explain format expectations (e.g., file paths, wildcards) or validation rules. With low coverage, the description provides basic mapping but insufficient detail for confident parameter usage.

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 ('check') and resource ('expected PIX4Dmatic outputs'), specifying it verifies existence under a project directory. It distinguishes from siblings like 'pix4d_get_status' or 'pix4d_find_log_errors' by focusing on output file validation rather than system state or error detection. However, it doesn't explicitly contrast with all siblings, such as 'pix4d_collect_diagnostics' which might overlap in file checking.

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., after 'pix4d_run_job'), exclusions (e.g., not for checking log files), or comparisons to siblings like 'pix4d_get_status' for broader status checks. The context is implied (post-processing verification) but not stated, leaving the agent to infer usage scenarios.

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