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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is largely covered; readOnlyHint=false is not contradicted by the description, which describes a computation rather than a read. The description adds real context by disclosing that candidates are judged against Eiken's PrimerExplorer V5 criteria, but omits the significant behavior that nearly every tuning knob defaults to a GC-class preset and that PrimerExplorer and the Eiken genome site disagree on some limits.

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?

One well-formed sentence, front-loaded with the action and the deliverable, with the judging criterion trailing as useful qualification. No filler, no repetition of the title, nothing to cut.

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?

For a tool with 24 parameters, 0 required fields and a nested _subject object, the description never states what input is minimally needed to run a design (a sequence, accession, sample id or file, optionally scoped by region_start/region_end). An output schema exists so return values need no explanation, but the omission of the input requirement leaves a real gap for an agent facing an all-optional schema.

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 description coverage is 100%, so the schema already carries the semantics of all 24 parameters, including the GC/Tm/length windows and the PrimerExplorer-vs-Eiken disagreement notes. The description only restates the F3/B3/FIP/BIP output set and the optionality of loop primers, which maps loosely to the loop_primers flag but adds no new parameter meaning. Baseline 3 applies.

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?

Specific verb plus specific resource: 'Design LAMP primer SETS' with an explicit product inventory (F3, B3, FIP, BIP plus optional loop primers) and the criteria used to judge them. The word LAMP (isothermal) clearly separates it from the many PCR/qPCR primer siblings like design_primers, design_primer_pairs and design_qpcr_assay.

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?

Usage is implied rather than stated: an agent can infer this is the tool for isothermal LAMP assays and that loop primers are optional, but the description names no alternatives and gives no when-not guidance (e.g. use design_primers for PCR, or design_bisulfite_primers for methylated templates). With ~20 primer-design siblings, an explicit routing sentence would have been valuable.

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