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

Annotations are empty, so the description carries the responsibility. It discloses in-silico-only behavior, RUO status, usage restrictions, and the fact that it is freely open to agents. It does not explicitly state side effects or that no data persists, but the in-silico modeling statement covers the main safety profile.

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?

Purpose is in the first sentence, followed by concrete method details, then compliance. No filler or repetition; every sentence carries distinct information.

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?

The description gives purpose, algorithm behaviors, host context, compliance constraints, and access policy. It does not state the output/return format or default host, but the schema already covers host options. Slightly lacking an explicit success/response description, otherwise complete.

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?

Input schema already documents all three parameters with clear descriptions (including host enum). The description adds useful context—protein vs cDNA input and GC-content harmonization—but does not clarify defaults or format details beyond the schema. This meets the baseline without extending it.

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?

Names a specific operation (optimize), the exact input types (protein amino acid or cDNA coding sequence), the goal (maximal recombinant expression yield), and the target host context. The method list (CAI, GC harmonization, restriction-site avoidance, leader generation) leaves no ambiguity about what the tool does.

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?

Clear use context: optimizing coding sequences for expression in a listed host. States explicit prohibitions (select-agent/regulated sequences) and the RUO/in-silico constraint. No alternatives or sibling comparisons are given, so it does not fully meet the 'when to use vs alternatives' bar.

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