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

The annotations already declare this is a read-only, closed-world, non-destructive operation, so the safety profile is covered. The description adds genuinely new behavioral context by stating the diagram comes from a real algorithm engine rather than LLM generation, which tells the agent the output is deterministic and trustworthy. It does not say what output format (image, SVG, code) is returned, which leaves a small gap.

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?

Two short clauses in brackets: the scenario/trigger first, then the return value with the engine note. Zero filler, and the most decision-relevant information is front-loaded.

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?

Given 8 all-optional parameters at full schema coverage, annotations covering the safety profile, and no output schema, the description says enough to call it correctly. The one meaningful omission is that all parameters are optional, so the description never indicates whether a minimal call (e.g., only screened and randomized) produces a valid partial diagram or degrades.

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 coverage is 100%, and each of the 8 parameters has a Chinese description that is essentially mirrored by the description text (screening, randomization, loss-to-followup). No additional semantics such as defaults, interdependencies, or what happens when a parameter is omitted are provided, so the baseline 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 states a specific verb+resource pair: draw a CONSORT flow diagram from screening/randomization/loss-to-followup counts. That is far more informative than the name alone. It stops short of a 5 because the nearest sibling, act_prisma_flow, is a closely related flow-diagram tool and the description never says how CONSORT differs from PRISMA or from act_forest_chart.

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?

It gives a clear trigger condition: the user has screening, randomization, or loss-to-followup numbers and wants a CONSORT diagram. There is no explicit when-not guidance and no named alternative for cases where the user actually needs a PRISMA diagram, so routing depends on the agent already knowing the study type.

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