streamelements_type

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

No annotations are supplied, so the description carries the entire burden and leaves key behaviors unstated: whether typing overwrites or appends to existing field content, whether it triggers input/change/submit events, whether focus is required first, and what happens on an invalid field number. For a mutating UI-automation tool with zero annotation coverage this is a significant gap.

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?

A single front-loaded sentence with no filler and no redundant restatement of the tool name. Every word carries information about the action and the target.

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?

With no annotations, no output schema, and no statement of side effects or return behavior, an agent cannot tell what this tool reports back or how the page changes after typing. For a browser-automation mutation tool, the definition should disclose more than the action alone.

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, including the useful 'Field number from the last read' hint. The description adds nothing beyond restating 'numbered field' and 'text', so the schema does the work and the baseline of 3 applies.

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?

Names a specific verb ('Type text') and a specific target ('a numbered field on the current StreamElements page'), which distinguishes it from streamelements_click and streamelements_read. It stops short of explicitly naming which sibling to use when, but the action itself is unambiguous.

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 'on the current StreamElements page' implies a prerequisite (a page must already be open) and 'numbered field' implies a prior read, but neither is stated as a rule. There is no explicit when-not guidance or comparison with siblings such as streamelements_click, which an agent would need to choose between.

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