get_target_pathways_and_go_terms

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

The readOnlyHint annotation already communicates the safe, non-mutating nature. The description adds the behavioral scope (listing pathway memberships and GO annotations) but does not disclose pagination behavior, default limits, or any filtering constraints. Since annotations cover the safety profile, this is acceptable but not rich.

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 a single front-loaded sentence with no wasted words. It immediately states the verb and the resource, and avoids any filler or repetition of the tool name.

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?

The presence of an output schema and the readOnlyHint reduces the need to describe return values. Still, the description lacks usage context and does not mention pagination, which is relevant given the page_size and page_index parameters. It is minimally complete for a simple read-only list tool but has clear gaps in guidance.

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 0%, and the description does not explain any of the three parameters (ensembl_id, page_size, page_index). While parameter names are somewhat self-explanatory, the description does not compensate for the lack of schema documentation or clarify that ensembl_id is the target identifier.

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 a specific verb ('List'), a resource ('pathway memberships and Gene Ontology annotations'), and a scope ('for a target'). This distinguishes it from sibling tools like get_gene_ontology_terms, which likely returns GO terms without pathway context, and other get_target_* tools that focus on different data.

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 gives no explicit guidance on when to use this tool versus alternatives such as get_target_info or get_gene_ontology_terms. It does not state exclusions, prerequisites, or situations where a different tool would be more appropriate. The usage context is only implied by the tool name.

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