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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds almost nothing beyond that: 'RETURNS: 质粒图谱' merely restates the tool name rather than disclosing the output form (image, SVG, feature table) or any constraints on input sequence length or format.

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 pipe-delimited layout is front-loaded and scannable, which is good. However, the long ALIASES list and the 'RETURNS: 质粒图谱' segment consume space without informing the agent, so the text is not fully economical.

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?

This is a read-only transformation tool with no output schema, so the description must explain what comes back. Instead the RETURNS field is a tautology, leaving the agent unable to tell whether the result is an image, a coordinate list, or an annotated sequence.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains it and the baseline of 3 applies. The description adds no extra meaning, such as accepted sequence formats (FASTA vs raw) or whether annotation is automatic.

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 gives a specific verb and resource: 'draw/describe a plasmid map from a sequence (features, orientation)'. That is enough to distinguish it from unrelated siblings, but it does not differentiate it from adjacent bioinformatics tools such as restriction_sites or cloning_design, so it stops short of a 5.

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 'USE WHEN' clause states an explicit trigger condition (you have a sequence and want a map with features/orientation). There is no when-not guidance and no named alternative for overlapping cases like restriction mapping or cloning design, so it is clear but incomplete.

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