gtex_eqtl

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

Annotations already establish readOnly and openWorld intent. The description adds meaningful behavior: exact output fields, p-value sort order, GTEx v10 data source, and the required tissue constraint. This goes well beyond annotations, though it does not discuss pagination or significance threshold semantics.

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 compact sentences with no filler. The core action, output shape, and sort order are front-loaded; the required parameter note is placed at the end. Every sentence 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 modest list-style query with a well-documented schema and read-only annotations, the description fully supports correct invocation: what the tool returns, how results are sorted, what the required tissue value should look like, and what gene identifiers are acceptable. No critical gap remains.

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?

Input schema covers all three parameters with clear descriptions and a required array. The description reinforces tissue formatting with examples, but does not materially extend parameter meaning beyond what the schema already provides. Baseline 3 applies.

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?

States a specific verb ('Get'), a specific resource ('significant cis-eQTL associations for a gene in a specific GTEx tissue'), and useful operational details (output fields, sorting order, data version). This clearly distinguishes it from sibling tools such as gtex_expression or gene-level lookups.

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 clear context for use: it is for cis-eQTL associations in a specified GTEx tissue. It explicitly notes that tissue uses a tissueSiteDetailId and gives examples. It does not explicitly name alternatives or when-not-to-use conditions, so it misses the top bar.

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