pt_type_text

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

With no annotations, the description fully discloses the paste and keyboard strategies, their trade-offs, and React Native compatibility. It also mentions auto-tap focusing, which is important behavioral context beyond what the schema provides.

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 front-loaded with the main purpose, followed by structured strategy blocks and a concise important note. Every sentence is actionable and there is no wasted content.

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?

The tool has 6 parameters and no output schema or annotations. The description covers usage flow, strategy selection, and focus behavior, but omits explicit return/error handling and does not mention sibling alternatives like pt_fill_input. Still, it is reasonably complete for a typing tool.

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 all six parameters, so the baseline is 3. The description adds meaningful context for x/y coordinates (auto-tap to focus) and strategy (recommended vs faster but incompatible), which elevates it above the baseline.

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 tool types text into the currently focused field or after tapping a field, using a specific verb and resource. It distinguishes from sibling tools like pt_tap by focusing on text entry, even though it doesn't explicitly name alternatives.

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?

Provides clear guidance on when to use the paste vs keyboard strategy, with a strong recommendation for React Native apps. It also explains the coordinate auto-tap behavior, but does not explicitly contrast with sibling tools like pt_fill_input or state when not to use this tool.

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