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

With no annotations, the description carries the full burden and does so: it declares the method is a sequence-motif rule set, explains that solvent exposure/flexibility/pH/temperature modulate real rates, warns that a buried NG can be stable while an exposed ND is not, and instructs the agent to treat output as a site list to test rather than a rate. This is exactly the epistemic-boundary disclosure an agent needs to avoid misusing the output.

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-loaded with purpose, then motifs, then usage, then the limitation caveat — a logical order with no wasted sentences. Slightly verbose in the framing clause ('the single most cited chemical-degradation CQA') and the caveat paragraph is long, though it earns its place given the absence of annotations.

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?

An output schema exists, so return-value explanation is not required, yet the description still summarizes the return shape and sort order. Combined with the motif list, usage contexts, and methodological caveats, an agent has everything needed to call and correctly interpret this single-param tool.

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 in 1-letter code, which adds real meaning. The second parameter (api_key) is left unexplained, which is the only gap; for a self-evident credential parameter this is minor.

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 verb+resource ('Locate asparagine deamidation hotspots in a protein sequence') and enumerates the exact rule set applied (NG/NS/NH/ND/NA/NT motifs with lability ordering), which distinguishes it from nearby siblings like covabio_cleavage_sites or covabio_protein_profile. An agent knows precisely what analysis is performed without opening the schema.

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?

Gives three concrete use cases (justify a deamidation-monitoring strategy, compare candidate sequences before lead selection, explain a charge-variant shift on IEX/icIEF) and a scope exclusion ('not a structural or kinetic prediction'). It does not name specific alternative sibling tools for adjacent needs, so it stops short of a 5.

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