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 monitoring CPU and logs for idle detection, but lacks details on behavioral traits like timeout handling, polling behavior, error conditions, or what 'idle' means operationally. This leaves gaps for an agent to understand how the tool behaves beyond basic purpose.

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 conveys the core purpose without unnecessary details. It's front-loaded and wastes no words, making it easy for an agent 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 5 parameters with 0% schema coverage and no annotations, the description is incomplete—it doesn't explain parameters or behavioral nuances. However, an output schema exists, so return values are covered. The description provides basic context but lacks depth for a tool with multiple configuration options.

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 doesn't mention any parameters, leaving all 5 parameters undocumented. The description hints at monitoring criteria (CPU and logs) but doesn't map to specific parameters like 'idle_cpu_percent' or 'poll_sec'. Baseline is 3 due to high schema coverage expectation, but the description adds minimal value.

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 tool's purpose: 'Wait until PIX4Dmatic appears idle based on process CPU and recent logs.' It specifies the action (wait), the condition (idle), and the monitoring criteria (CPU and logs). However, it doesn't explicitly differentiate from siblings like 'pix4d_get_status' which might check status without waiting.

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 implies usage when needing to wait for PIX4Dmatic to become idle, such as after launching a job. It doesn't provide explicit alternatives or exclusions, but the context suggests it's for monitoring idle state, unlike siblings focused on actions like 'pix4d_run_job' or 'pix4d_get_status'.

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