start_element_observation

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that observation is continuous and scoped to subtree/ancestors, but omits side effects, duration, idempotency, prerequisites for identifying the element, and how observation ends.

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 concise, front-loaded sentence with no redundant wording. It is appropriately sized and every word contributes meaning.

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 output schema and no annotations, an agent needs more context: how to choose the target when required parameters are zero, what continuous observation implies for resource use, and how to stop it. The sibling set shows related observation tools, but the description does not mention them or the overall workflow.

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 100%, so both parameters are already documented. The description adds little beyond 'target element' and does not clarify whether nodeId and selector are alternative or complementary ways to identify the target, especially since neither param is required.

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 uses a specific verb ('Start') and resource ('focused continuous recording and observation') and scopes it to a target element plus its subtree/ancestors. It is clear, but it does not explicitly distinguish this from sibling tools like start_element_picker or trace_element.

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 phrase 'continuous recording and observation' implies this is for long-lived observation of an element, which is the correct context. However, it gives no explicit when-to-use guidance, no exclusions, and no mention of the matching stop_element_observation tool that would complete the workflow.

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