replace_text

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

In the absence of annotations, the description carries the full burden of disclosure. It honestly states that the tool clears current text before typing, but does not describe potential side effects, failure modes, or requirements (e.g., device must be unlocked, text field must be focused). The description is minimally transparent.

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 that conveys the core functionality without extraneous words. It is front-loaded with the action and meets the conciseness standard perfectly.

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 tool with one parameter, no output schema, and no annotations, the description covers the basic function but lacks details on error conditions, prerequisites (e.g., text field focus), and behavior when no text is present. It is minimally complete but not comprehensive.

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?

The parameter 'text' has no schema description (0% coverage). The description compensates by implying that 'text' is the new text to type ('typing new text'). This adds meaning beyond the raw schema, but does not specify format, length limits, or whether special characters are allowed. Adequate for a simple parameter.

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') and the resource ('on the connected Android device'), including the method ('clearing current text and typing new text'). However, it does not differentiate from the sibling tool 'clear_and_type_text', which appears to perform the same operation.

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 guidance is provided on when to use this tool versus alternatives like 'type_text' or 'clear_and_type_text'. The description simply states what it does, but does not cover prerequisites (e.g., requiring a focused text field) or scenarios where it is appropriate.

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