test_paste_strategy

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

Without annotations, the description warns about the injection into the focused window, explains returns (timing + success flag), and instructs safety precautions. Lacks details on edge cases like no window focused.

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?

Two concise sentences with a front-loaded warning and clear, essential information; no wasted words.

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?

Given one parameter and no output schema, the description fully explains purpose, return values, and a critical safety condition, making it complete for a test 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 covers the single parameter with a description linking to list_paste_strategies; the tool description adds no further parameter details, so baseline 3 applies due to high schema coverage.

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?

Describes injecting test text into the focused window to verify a paste strategy, which clearly distinguishes it from sibling tools like list_paste_strategies or set_paste_strategy.

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?

States to use for verifying a strategy on the machine, and provides a prerequisite to focus a safe target. Does not explicitly exclude alternative tools but gives clear context.

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