Reads local prerequisites for Microsoft Edge IE mode automation without altering system settings, helping you verify setup before running Selenium and IEDriver tasks.
Read local prerequisites without changing system settings.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does disclose the key safety trait: it does not change system settings. That is genuinely useful. However, it says nothing about what is inspected, whether anything is executed/spawned during the check, or how long it takes.
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?
A single tight sentence with the read-only constraint front-loaded. Nothing wasted, though there is also very little substance.
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?
There is no output schema, so the description is the only place an agent could learn what this returns (which prerequisites, pass/fail shape, diffable facts) — and it says nothing. For a diagnostic tool, the returned information is the whole point, and it is missing.
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?
Zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline for a no-arg tool applies.
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?
"Read local prerequisites" names a read operation and a rough resource, but "prerequisites" is left undefined — an agent cannot tell whether this checks browsers, drivers, paths, or environment variables. It is distinguishable from the browser_* siblings only by implication (it does not drive a browser).
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?
There is no statement of when to call this versus the browser_* tools, no prerequisites, and no mention of whether to run it before browser_start. Usage is left entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.