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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without description help. The description adds that outputs are derived artifacts (GenBank qualifiers, OpenCloning JSON, a runnable QUEEN script) but says nothing about size, latency, or what happens when the record lacks construction history — details that actually live in the schema's refusal note.

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?

It is a single front-loaded sentence with the verb first, which is good structure. However, the seven-item enumeration largely duplicates the already verbose `format` enum descriptions in the schema, so a meaningful share of the sentence does not earn its place.

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 an output schema present and 100% parameter coverage, the description only needs to establish purpose and the format space, and it does both. The remaining gap — when to prefer this over the history/verification siblings — is minor for a read-only exporter.

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 100%, so the baseline is 3, but the description goes slightly further by mapping each prose artifact ('a step spreadsheet', 'the molecule carrying its own history as GenBank qualifiers', 'the runnable QUEEN script that rebuilds it') onto the enum values, giving an agent an intuitive read on format choices. It says nothing about _subject, document, or sbol_syntax, which are left entirely to 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 uses a specific verb+resource ('Write a construct's recorded build out as a document') and enumerates the seven concrete artifacts produced, which is distinctive among siblings like get_construction_history or build_assembly_report. It stops short of naming a sibling to contrast with, so an agent must still infer the boundary from the format list alone.

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 only implied: the phrase 'recorded build' suggests this is a post-assembly export step, but there is no explicit when-to-use versus get_construction_history, history_protocol, or compare_constructions. The real routing guidance (methods is the only format every source can produce; unsupported formats are refused by name) lives in the schema, not the description.

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