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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds value beyond those by disclosing companion counts (study count, direct parent count, direct descendant count) and interpreting them as signals for pedigree depth and observation coverage — context an agent would not derive from the annotations or the schema.

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 filler: the core purpose is front-loaded in the first clause, and the second sentence adds genuinely useful interpretive context about the response companions. Every clause 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?

For a simple 2-parameter read with full annotations, 100% schema coverage, and an output schema present, the description is nearly complete — it names the response contents and explains why those contents matter. The only real gap is the absence of explicit routing between this tool and its close siblings brapi_find_germplasm and brapi_walk_pedigree.

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%, with both alias and germplasmDbId well documented in the schema, so the baseline of 3 applies. The description confirms germplasmDbId as the lookup key but contributes no additional format, constraint, or usage detail beyond what the schema already states.

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 and resource ('Fetch a single germplasm by DbId') and specifies what is included (attributes, direct parents), so an agent knows exactly what the tool does. The 'single... by DbId' phrasing signals a point lookup as opposed to the search-style brapi_find_germplasm sibling, though no sibling is named explicitly.

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?

When to use is implied: an agent has a specific germplasmDbId and wants that one record with its attributes and parents. The second sentence hints at suitability for pedigree and observation-coverage questions, but there are no explicit alternatives, exclusions, or guidance about when to prefer brapi_walk_pedigree or brapi_find_germplasm.

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