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

Goes well past the readOnly/openWorld/idempotent annotations: it discloses that boxes are auto-derived and marked as derived, that arithmetic is validated with a warning naming each inconsistent box and its expected value, and that the diagram renders the given numbers verbatim. These are exactly the runtime behaviors an agent needs to interpret results.

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?

Five sentences, each carrying distinct information (outputs, partial input, derivation, validation, second column), with the core action front-loaded. Dense but with no filler; the sentence count is justified by the breadth of behavior covered.

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 nested-schema tool with an output schema, this covers purpose, output formats, validation behavior and the conditional column well enough to call correctly. It stops short of explaining the footnote toggle or the explicit force-on/off flag, minor gaps given the schema describes them.

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 67% and the description meaningfully complements it by explaining derived-box filling, the validation contract, and that otherMethods drives the second column (websites, organisations, citation searching). The footnotes and other_methods_column flags are not addressed, which keeps this below a 5.

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?

States a concrete verb and resource ('Draw a PRISMA 2020 flow diagram... from the record counts') plus the concrete outputs (PNG, SVG, download links). Nothing in the sibling set (check_retractions, format_citations, search_papers, verify_references) overlaps, so the agent can select this unambiguously.

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?

'Give the counts you have' tells the agent it may supply a partial set, and the closing sentence names the condition for the second column. There is no explicit when-not or named alternative, but the tool has no real competitors among its siblings, so the routing context is clear.

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