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

No annotations, so the description carries the full burden. It discloses the operations and the two codon-usage optimizations, which is useful behavior, but says nothing about the api_key authentication requirement, cost, rate limits, or limitations of the 'simple' domain search.

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?

Front-loads the toolbox purpose and packs the operations into one dense, mostly waste-free paragraph. The trailing 'Returns:' block partially duplicates the existing output schema, a minor redundancy.

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 multi-function toolbox with an output schema but no annotations, the description adequately covers what each function does and the intended workflow. Only the undocumented api_key and the absence of any sibling routing keep it from being fully 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?

Schema description coverage is 0%, so the description must compensate. It documents 'sequence' as a protein amino acid sequence, which is helpful, but the second parameter (api_key) is neither in the schema text nor the description, leaving a gap for a tool that evidently needs auth.

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?

States a specific resource and enumerates the concrete operations (code conversion, codon table, reverse translation for E. coli/human, signal-peptide check, domain search, restriction sites) and the goal ('protein sequence to an expression construct'). It is distinguishable from most siblings, though it overlaps with covabio_codon_adaptation and covabio_cleavage_sites without naming them.

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?

'Use when going from a protein sequence to an expression construct' gives situational context, but with dozens of bio siblings (covabio_codon_adaptation, covabio_cleavage_sites, covabio_protein_profile) there is no explicit when-not or named alternative to route the agent. Usage is implied rather than delimited.

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