Adobe Firefly DOM Watcher

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

No annotations provided, so description carries full burden. It describes what it does (watch mutations) but omits side effects, permissions, rate limits, or how 'reports' are delivered. Lacks clarity on whether it modifies state, which is critical for a monitoring tool.

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?

Two concise sentences with minimal waste. Front-loaded purpose. However, second sentence is somewhat generic and could be more specific without increasing length.

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?

No output schema exists, so description should explain return value behavior. It does not. Parameter details are complete (100% coverage). For a watch tool, lack of output format is a notable gap. Moderately complete.

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 covers all 4 parameters with descriptions. The description adds a usage example ('buttons load or spinners disappear') that helps understand targetSelector, but overall does not add substantial meaning beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states 'Watch for DOM mutations' and specifies what is reported (elements appear, disappear, attribute changes). Verb-resource combination is precise, and it distinguishes from sibling tools like firefly_dom_inspect (inspection) and generation tools.

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?

Provides use-case context ('knowing when buttons load or spinners disappear') but lacks explicit when-to-use/when-not-to-use guidance or comparisons to sibling tools. No alternatives or prerequisites mentioned.

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