set_text

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions focusing the control and firing editing-change events, which are important side effects. However, it does not describe post-action waiting behavior or potential issues, despite the schema including many wait parameters.

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 sentence with no filler, efficiently communicating the core action, target, and side effects. It is appropriately concise and 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?

Despite the core action being clear, the description lacks context on when to use this tool versus type_text and does not mention the built-in waiting/timeout behavior after setting text—important given the many wait-related parameters. No output schema exists, so the description should have provided more post-condition context.

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 the schema fully documents all 11 parameters. The description adds little beyond the schema, only clarifying that 'id' is a stable identifier and the action is to replace text. It does not elaborate on timeout or wait parameters, but the schema already does.

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 (replace text), target (UITextField/UITextView), method (by stable DebugBridge ID), and side effects (focusing, firing editing-change events). This specificity distinguishes it from siblings like type_text, which likely simulates typing rather than replacing.

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?

No explicit guidance is provided on when to use this tool versus alternatives like type_text or tap_element. The description does not state prerequisites, exclusions, or preferred scenarios, leaving the agent to infer usage from the name and schema.

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