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

Annotations already declare readOnly/openWorld/destructive=false, so the safety profile is covered. The description adds real behavioural value beyond that: it discloses the two artifacts produced (an .embl flat file and its manifest) and the target consumer (Webin-CLI `-context sequence`). It stops short of saying where files land or what the return looks like, though an output schema exists.

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 sentence, front-loaded with the transformation and immediately followed by the concrete outputs and CLI context. No filler, nothing restated from the name.

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 10-parameter tool with nested objects, annotations and an output schema, the description covers what it produces and which submission context it serves, which is the essential framing. The heavier prerequisites (study accession required by Webin-CLI, taxonomy checks) are carried by the schema descriptions, so the remaining gap is minor.

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% across all 10 parameters (including the nested `_subject` and `_files` shapes, study accession, mol_type, topology), so the schema does the heavy lifting. The description adds no parameter-level meaning beyond the schema; 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+resource: it converts a record into an ENA flat file (`.embl`) plus a manifest, targeting Webin-CLI `-context sequence`. That names the output artifacts and the exact submission flavour, which cleanly separates it from siblings like build_genbank_submission and build_addgene_deposit.

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 mention of `-context sequence` implies the scenario (annotated sequence submission via Webin-CLI) rather than genome/other contexts, so usage is implied. But there is no explicit when-to-use/when-not-to-use guidance and no routing to build_genbank_submission for the GenBank alternative.

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