create_venn_diagram

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

The description details the output (side-by-side Venn diagrams for up and down regulated genes, link to plot, summary statistics) and includes a formatting instruction. No annotations are provided, so the description carries the burden, and it adequately covers behavior without contradictions.

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 description is well-structured with bullet points and clear sections, front-loading the purpose. The FORMATTING INSTRUCTION is somewhat extraneous but not overly verbose. It could be slightly more concise, but it remains efficient.

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 the tool has 6 parameters, no annotations, and an output schema, the description fully covers the behavior, expected input, and output. It explains the up/down regulation logic and return value, making it complete for an AI agent.

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 the schema already describes each parameter. The description adds context by explaining the effect of assay_id_3 and the threshold, but this is largely redundant with the schema. Baseline 3 is appropriate.

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 clearly states it creates Venn diagrams for comparing differentially expressed genes between 2 or 3 assays, specifying the up/down regulation distinction. This distinguishes it from siblings like create_volcano_plot and find_common_differentially_expressed_genes.

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 description explains when to use the tool (comparing DE genes) and how the number of assays affects the output (2-way vs 3-way). However, it does not explicitly state when not to use it or compare with alternatives like find_common_differentially_expressed_genes.

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