transfer

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

With no annotations, description fully discloses the operation sequence (pick up tips, aspirate, dispense, drop tips) and constraints (same well count, at most one column). Provides clear behavioral model.

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 sentences, efficient and front-loaded: first sentence states action and process, second adds constraints. No redundant information.

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?

Provides key behavioral and constraint details for a 4-parameter tool with no output schema. Missing explanation of 'tips' parameter and potential errors, but covers essential usage.

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 0%, so description carries burden. Explains source, dest (ranges), volume (microliters), but does not explain the 'tips' parameter (e.g., tip reuse or type). Partial 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?

Clearly states the tool transfers liquid from source to dest wells, with explanation of the head pass process. Distinguishes well from sibling tools like aspirate, dispense, pick_up_tips, and drop_tips.

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?

Implied usage as a combined operation, but no explicit guidance on when to use transfer versus performing separate steps. Lacks alternative suggestions.

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