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 known. The description adds one meaningful behavioral constraint (assembled only from analyses actually run, implying no fabrication), but it never explains where the analyses are drawn from given zero parameters, nor what 'RETURNS: 论文段落' yields concretely.

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?

The pipe-delimited layout front-loads the use case and keeps the whole definition to a few short segments with no filler prose. The repeated bilingual title and the minimal 'RETURNS: 论文段落' segment contribute little beyond decoration.

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?

With no parameters, no output schema and a closed-world annotation, the description must carry the whole burden of explaining inputs and outputs. It states the source constraint but not how the analyses are located or what the returned paragraph looks like, leaving a real gap for an agent trying to invoke it correctly.

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 tool takes zero parameters, so there is no parameter semantics for the description to carry and the baseline of 4 applies. The one related gap is that the description does not say how the tool obtains its input context, which matters more here than for a parameterized tool.

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: drafting a methods section for a multi-omics paper, and it constrains the content to analyses the user actually ran. It does not explicitly distinguish itself from siblings like proteomics_methods_draft or section_writer, leaving the agent to infer the multi-omics scope from the name alone.

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 'USE WHEN' clause gives clear triggering context: the user wants a methods section for a multi-omics paper. It stops short of stating when NOT to use it or naming the obvious alternative (proteomics_methods_draft, section_writer) for single-omics or non-methods writing.

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