sassy_type_text

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

Goes far beyond the destructiveHint annotation by disclosing the exact destructive mechanism: it 'always clears the field first with ctrl-a + backspace, so it never appends'. It also reveals the conditional click on target_x/target_y, per-keystroke interval, platform support, and return value, all consistent with the annotations.

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?

Six sentences, each earning its place: purpose, destructive behavior, coordinate/interval behavior, platform, return value, and sibling routing. It is front-loaded with the most important facts and contains no filler.

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?

Covers purpose, destructive behavior, parameter conditions, platform, return value, and alternatives. Given that an output schema exists and annotations capture the safety profile, nothing an agent needs to invoke this tool correctly is missing.

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?

With 0% schema description coverage, the description carries the full burden, and it succeeds: text is the typed content, interval is the seconds between keystrokes with a default, and target_x/target_y jointly trigger a preliminary click only when both are nonzero. This adds actionable meaning beyond the bare schema.

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?

States a specific verb and resource: 'sends keystrokes to the focused field' and 'fill GUI fields'. It also distinguishes itself from siblings by naming sassy_hotkey for shortcuts and sassy_click for mouse actions, so an agent can select correctly.

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 explicit when-to-use guidance ('Use it to fill GUI fields') and explicit when-not guidance ('if you need to preserve existing content, this is the wrong tool'). It also names concrete alternatives, sassy_hotkey and sassy_click, reducing ambiguity.

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