Summarize sequence

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds that it summarizes composition and GC-related metrics, which is useful context but does not detail additional behavior like output format or side effects, though the output schema likely covers that.

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?

A single sentence that directly states the tool's function without waste. Every word contributes meaning.

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 simple, single-parameter tool with complete schema coverage, annotations, and an output schema present, the description sufficiently conveys the tool's scope. It covers the key outputs and there are no obvious gaps.

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?

The schema fully documents the single 'sequence' parameter, including accepted formats (raw or FASTA), IUPAC codes, and length limit. The description adds no parameter information, so the schema carries the burden, meeting the baseline.

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 uses the specific verb 'summarize' with the resource 'sequence' and names specific outputs: composition, GC uncertainty, and GC skew. This clearly distinguishes it from siblings like scan, enumerate, reverse complement, and translate.

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 description implies this is for obtaining a summary of sequence characteristics but does not explicitly state when to use it over alternatives. No exclusions or alternative tool references are given, but the distinct purpose is self-evident.

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