Render Concept Diagram

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered without help from the description. The description adds real value by disclosing what the diagram must contain (concrete numeric example and the analogy failure boundary), but says nothing about the rendered output form (image, SVG, mermaid, markup) or whether rendering can fail.

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?

A single front-loaded sentence with no filler: verb, artifact, and contents in one pass. It is efficient, though for a seven-parameter rendering tool it is arguably too terse to be fully 'appropriately sized'.

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?

No output schema exists, so the description carries the burden of saying what a 'render' returns, and it does not. For a tool with seven required structured inputs sitting among four similar render_* siblings, the agent is left without return-format or routing information.

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 71% and every one of the seven required parameters carries its own description, so the schema does most of the work. The description only gestures at the parameter set (类比, 例子, 失效边界) without adding format, sizing, or dependency rules (e.g. 1-3 mappings, 2-4 mechanism steps) beyond what the schema enforces.

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 (绘制/render) and a specific artifact (生活类比↔科学机制映射图) plus the required contents (具体例子、类比失效边界), so an agent knows exactly what gets produced. It does not, however, distinguish itself from the four sibling render_* tools (paper map, section flow, formula structure, evidence prism), which is the one thing an agent must decide between here.

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?

There is no statement of when to choose this over render_paper_map, render_section_flow, render_formula_structure, or render_evidence_prism, and no prerequisites or trigger conditions. The only hint is the phrase 晦涩概念, which weakly implies the tool targets hard-to-grasp concepts, but no explicit guidance or exclusion is given.

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