browser_prepare_legacy_row

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

With no annotations, the description carries the full burden and does substantial work: it discloses the copy scope (existing underscore-prefixed attributes only), the rejection conditions, and explicit non-behaviors (does not change values, click, submit, or persist across reloads). It still omits error/return shape and whether the DOM change is reversible short of reload.

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?

Four dense sentences, front-loaded with the operation, then scope, then exclusions, then the precondition gate. Little waste, though the jargon-heavy opening ('visible TR', 'old handler') costs a beat of parsing.

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 niche DOM-mutating repair tool with no annotations and no output schema, the description covers intent, scope, exclusions, and gating. The remaining gap is the unexplained 'ref' parameter and the absence of any return/failure signal, which matters for a tool that intentionally rejects inputs.

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 coverage is 0% for both parameters. The description implies the 'attributes' array is filtered to existing underscore-prefixed entries, which is useful, but it never explains what 'ref' refers to (element reference format) or whether the array is a candidate list or an exact spec. Partial compensation for a total schema gap.

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 specific verb and resource: it repairs a visible TR row so its legacy handler can read custom attributes as properties (row._id), by copying underscore-prefixed attributes. No sibling tool does anything comparable, and the IE11 compat framing separates it cleanly from generic DOM tools like browser_inspect_element or browser_fill.

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?

It states a hard precondition: 'Use only after inspecting the handler and diagnosing this IE11 incompatibility,' which effectively rules out speculative use. It also notes the rejected cases (missing attributes, conflicting properties). It does not name a concrete alternative action, so it falls short of a 5.

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