create_volcano_plot

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

With no annotations provided, the description carries full burden. It describes the return value (link and summary statistics) and explains the significance coloring logic. However, it does not disclose potential side effects (e.g., whether it modifies data) or authorization requirements, which are minor omissions given the tool's read-like nature.

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 concise and front-loaded with purpose. The formatting instruction is slightly unnecessary but does not detract significantly from clarity. Every sentence adds value.

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 presence of an output schema (not shown but implied by context signals), the description need not detail return values. It covers plot interpretation, threshold logic, and output type. Missing usage guidelines prevent a higher score, but overall it is sufficient for correct invocation.

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?

All 6 parameters have schema descriptions (100% coverage), so the baseline is 3. The tool description adds overall context (e.g., meaning of thresholds) but does not provide additional details per parameter beyond what the schema already offers.

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 that it creates a volcano plot for differential gene expression data, specifying the axes (log2 fold change vs -log10 adjusted p-value) and coloring logic. This distinguishes it from sibling tools like create_venn_diagram or find_differentially_expressed_genes, which serve different purposes.

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 implies usage for visualizing DE results but does not explicitly state when to use this tool versus alternatives like find_differentially_expressed_genes or create_venn_diagram. No guidance on prerequisites or when not to use it.

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