mcp-electron-driver

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

No annotations are provided, so the description carries the full burden. It states it's a read operation, implying non-destructive behavior, but doesn't disclose other traits like error handling, performance implications, or dependencies (e.g., needing a snapshot for 'ref'). This is insufficient for a tool with potential complexity in web interactions.

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 purpose and lists parameters, with no wasted words. It could be slightly more structured by separating usage hints, but it's appropriately sized for the tool's scope.

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 no annotations, no output schema, and incomplete parameter documentation (50% coverage), the description is inadequate. It doesn't explain return values, error cases, or behavioral nuances, making it incomplete for a tool that interacts with dynamic web elements.

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 50% (only 'ref' has a description), and the description adds that parameters are 'selector' or 'ref', matching the schema. However, it doesn't explain the semantics beyond this, such as what 'selector' expects or how 'ref' relates to snapshots, so it partially compensates but not fully, aligning with the baseline.

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 ('Read') and resource ('current value of a form input, textarea, or select'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_text' or 'get_attribute', which might retrieve similar content, so it doesn't reach a 5.

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 'get_text' or 'get_attribute', nor does it mention any prerequisites or exclusions. It only lists parameter options ('selector' or 'ref') without contextual advice, leaving usage unclear.

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