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 without the description's help. The description adds nothing beyond that: 'RETURNS: CONSORT 流程图' merely restates the title and leaves the actual return medium ambiguous (image file, Mermaid source, or structured data), which is exactly what an agent needs to know before invoking a diagram generator.

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 definition is short and front-loads the action verb, then scans cleanly through USE WHEN, ALIASES, and RETURNS. The 'RETURNS: CONSORT 流程图' line is pure redundancy with the title and wastes a slot that could carry output-format information.

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?

All eight parameters are optional, so an agent needs guidance on what happens when counts are omitted and what the finished artifact looks like; neither is addressed. With no output schema and a placeholder RETURNS line, the definition is adequate to identify the tool but not to predict its output.

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 all eight parameters already carry Chinese labels; the description only summarizes their categories ('screening/randomization/loss counts'). It adds no meaning beyond the schema, such as whether counts must be mutually consistent (screened = excluded + randomized) or how missing optional counts are rendered.

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 gives a specific verb and artifact ('draw a CONSORT participant flow diagram') plus the source data it consumes (screening/randomization/loss counts), so an agent knows exactly what the tool produces. It does not explicitly contrast with the closely related prisma_flowchart sibling, leaving the CONSORT-vs-PRISMA distinction to the agent's domain knowledge.

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 states a clear triggering condition tied to the study phase (participant flow counts from screening through loss to follow-up). There are no exclusion conditions and no named alternatives, so an agent unsure whether to use this or prisma_flowchart gets no routing help.

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