drop_tips

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether tips are returned to the rack for reuse or discarded, what happens if no tip is attached, or any side effects like tip ejection. The description is insufficient for an agent to understand the tool's impact.

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, which is concise but lacks structure (e.g., bullet points). It is front-loaded with the verb, but the brevity sacrifices clarity. It could be improved by adding a second sentence without being verbose.

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 the low complexity (1 parameter, no output schema) and no annotations, the description is incomplete. It does not mention prerequisites (e.g., must have tips attached), the tip rack specification, or cleanup. The agent is left with insufficient information to use the tool correctly in a workflow.

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%, and the description only uses the word 'range' to allude to the 'wells' parameter. It does not explain the parameter's format, default value, or meaning. For a single parameter, the description should specify how to specify the wells, but it fails to add value beyond the 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?

The description states the action 'Return tips' and the object 'tip rack', and mentions 'given range' which loosely maps to the 'wells' parameter. However, it does not explicitly state that this is for dropping tips from a pipette into specific wells, and the phrase 'Return tips' is ambiguous about whether they are recycled or discarded. It distinguishes from sibling 'pick_up_tips' but lacks specificity.

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. With siblings like 'pick_up_tips', 'aspirate', 'dispense', it is implied to be used after using tips, but the description does not address prerequisites or conditions.

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