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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the tool's safety profile is known. The description adds substantial behavioral context: the CSV columns, the plate type placeholder, the well-layout logic (row-major across a 384-well plate), and the assumption of a 5 uL reaction with explicit volume breakdowns. It also discloses that the plate type code is a placeholder, which is a non-obvious caveat. No contradictions exist.

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 dense but not wasteful. The first sentence captures the core purpose, and subsequent sentences provide important details (column names, volume assumptions, plate placeholder, well ordering). Every sentence adds value, though it is longer than strictly necessary and could be split into a summary plus caveats.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so thoroughly: it names the CSV columns, describes plate type placeholders, explains the source plate layout, and flags that the volume scale is not universal. It also references how positions relate to export_plate_layout, which gives richer context. The tool's assumptions and limitations are clearly stated.

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?

The schema covers 100% of the single parameter 'reactions' with nested object descriptions and a max of 96 entries. The description adds meaningful semantics beyond the schema by explaining how distinct template labels are assigned to unique wells and connecting the parameter to the output layout and volume assumptions. This goes beyond a baseline of 3.

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 begins with 'Generate a downloadable Beckman/Labcyte Echo acoustic-liquid-handler picklist CSV', which clearly states the action (generate), resource (picklist CSV), and target platform (Echo). It distinguishes from siblings like export_plate_layout and export_opentrons_protocol by specifying the exact output format and its association with Echo acoustic dispensing.

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?

The description gives clear context: it is for PCR reactions on an Echo acoustic liquid handler, and it aligns well positions with export_plate_layout. However, it does not explicitly mention when not to use it or name alternatives such as export_opentrons_protocol, so exclusions are absent. The context is strong, but the guidance could be more direct.

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