Store, retrieve, and list cached DOM selectors for e-commerce automation, reusing them across sessions to avoid re-querying elements and ensure stable script execution.
Manage cached DOM selectors
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| action | Yes | ||
| selectors | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, and it says almost nothing. It does not reveal whether operations read, write, mutate, persist, or clear cache state, nor does it mention side effects, permissions, or return behavior.
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 only one short phrase, which is technically concise, but it is under-specified rather than efficiently informative. It front-loads nothing useful because 'Manage' does not tell the agent what behavior to expect.
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?
For a tool with three parameters, an enum-based action, no output schema, no annotations, and many siblings, this description is severely incomplete. An agent could not reliably select or invoke this tool correctly based solely on the description.
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 for the undocumented parameters, but it does not. It never explains the meaning of 'key', the values of 'action', or how 'selectors' relate to the cached DOM selector map.
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 names a resource ('cached DOM selectors') and a general verb ('Manage'), so it is not a pure tautology. However, 'Manage' is vague and does not convey the actual get/set/list operations or differentiate this tool from sibling tools like ecommerce_visual_dom_analysis.
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?
No guidance is given about when to use this tool versus alternatives. The description does not state any context, prerequisites, or exclusions, leaving the agent to infer when 'managing cached DOM selectors' is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.