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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are reported ('report what was removed'), which hints at returned statistics rather than only trimmed reads. It does not disclose the important default that quality trimming is disabled (cutoffs default to 0), so a reader may expect quality trimming that does not happen unless parameters are set.

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?

One sentence, front-loaded with the action and resource, with the reporting clause appended efficiently. There is no filler, though the sentence could have used its length to flag the default-off quality trimming instead.

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 and the input schema is fully documented, so the description need not explain return values or parameters. Still, for an 11-parameter tool with nested record references, the description omits the default behavior (adapter-only unless quality cutoffs are set) and any pointer to alternatives like fastq_qc, leaving a meaningful gap.

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 100%, so every parameter including the advanced ones (min_overlap, max_error_rate, phred_offset, adapter_kind) is documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names a specific verb and resource: trim adapters and low-quality ends off FASTQ reads, plus report what was removed. The phrase 'before mapping' positions it relative to the mapping step (map_reads/align_read siblings) without naming them explicitly. It is clearly distinct from siblings like fastq_qc or demultiplex_reads, though no sibling is called out by name.

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?

'before mapping' implies the pipeline position where this tool belongs, which is useful context. However, there is no explicit when-not guidance, no mention of fastq_qc for pre-trim assessment, and no statement that quality trimming is off by default (both quality_cutoff_* default to 0). The usage context is implied rather than stated.

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