type

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

Discloses that it dispatches input and change events, which is key behavioral info. Without annotations, this is valuable. Could mention error handling or if it triggers other listeners, but sufficient for a simple input 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 short sentences: first explains the action, second gives usage context. No fluff, front-loaded.

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 simple tool with 2 required string params and no output schema, the description covers purpose and usage. Could mention what happens on invalid ref, but overall adequate.

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 100% with descriptions for both parameters. The tool description does not add extra meaning beyond the schema, so 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?

The description clearly states the action (Set value), the target (input/textarea), and the side effects (dispatches input + change events). It distinguishes itself from siblings like 'click' or 'submit' by specifying it's for form field input.

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?

Explicitly says 'Use before submit on form fields.', providing clear context for when to use this tool vs. alternatives like 'submit' or 'click'.

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