PIX4Dmatic MCP

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states it returns a 'compact' tree without detailing behavioral traits like performance impact, permissions needed, or how the tree is structured. It mentions 'selector discovery' but doesn't explain what selectors are or how the output aids in this, leaving significant gaps in transparency.

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 is front-loaded with the core purpose. Every word earns its place, with no wasted text, making it highly concise and well-structured for quick understanding.

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 has an output schema, the description doesn't need to explain return values, but it lacks details on behavioral context and parameter meaning. With no annotations and low schema coverage, the description is minimally adequate but has clear gaps in explaining how the tool fits into the broader UI automation workflow with siblings.

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 description adds no parameter semantics beyond the input schema, which has 0% description coverage and only one parameter 'depth' with a default. Since schema coverage is low (<50%), the description doesn't compensate by explaining what 'depth' means or its impact on the returned tree, resulting in a baseline score due to the single parameter.

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 ('Return') and resource ('UI Automation tree'), with the purpose 'for selector discovery' providing specific context. However, it doesn't explicitly differentiate from sibling tools like pix4d_screenshot or pix4d_focus, which might also relate to UI interaction, so it doesn't reach the highest score.

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, such as when to prefer it over pix4d_screenshot for UI inspection or how it relates to other UI-focused tools. It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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