list_top_level_pathways

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the return shape ('Dict {count, pathways}'), the top-level scope, and accepted species formats, but does not disclose potential errors, rate limits, or pagination behavior. This is acceptable for a simple read-only list tool but not richly transparent.

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 compact and well-structured, with a one-sentence purpose followed by concise Args and Returns sections. Every line adds useful information with no redundancy.

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 tool with one parameter and no output schema, the description covers the essential aspects: purpose, parameter format, and return shape. It does not discuss edge cases or error handling, but these are not critical for such a straightforward listing operation.

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?

The input schema only provides the parameter title 'Species', with 0% schema description coverage. The description compensates by explaining that species can be given as a name ('Homo sapiens') or NCBI taxId ('9606'), adding meaningful format guidance beyond the schema.

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 states a specific verb ('List') and resource ('top-level pathways for a species'), and clarifies that these are 'the browser's entry points'. This distinguishes it from sibling tools like list_pathway_events, which operate on events within pathways.

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 clearly indicates this is for listing top-level pathways for a species, giving a clear usage context. It does not explicitly mention alternatives or when not to use it, but the purpose is specific enough to guide selection.

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