get_germplasm_metadata

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

With no annotations, the description fully discloses behavior: reads attributes, writes a specific CSV file (germplasm_metadata.csv), and returns an empty-result note for certain builds (some 2.12). Mentions side effect (file writing) and limitation.

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 sentences with no wasted words. The first sentence is a clear one-liner; the second provides necessary detail on source, output, and edge case. Every part earns its place.

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 few parameters and an output schema (context indicates output schema exists), the description covers the core functionality, side effect (writing CSV), downstream usage, and a known limitation. No gaps.

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% (both parameters described). Description adds value by explaining output_dir default and variant_set_db_id format (MODULE§project§run), and that output is one row per accession.

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 fetches per-individual metadata (germplasm attributes) from Gigwa and writes a CSV. It distinguishes from siblings like import_metadata (which imports) and diversity tools (which consume the output).

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?

Provides context that metadata must be imported first via import_metadata or BrAPI, and that the CSV output feeds into grouping tools (diversity_fst/diversity_by_group). Does not explicitly state when not to use, but covers key usage conditions.

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