reactome_get_analysis_result

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions filtering and pagination capabilities, which is useful, but does not disclose safety, error handling, rate limits, or the non-mutating nature beyond the word 'Retrieve'. No details on what happens with an invalid token or how results are structured.

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 two sentences, front-loaded with the core action, and contains no redundant information. Every word contributes to understanding the tool's primary function.

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 complexity is moderate with 7 parameters and no output schema. The description gives a clear high-level purpose but does not explain the nature of the returned analysis result, possible response fields, or how filtering parameters interact. It is adequate for a simple retrieval but lacks details that would help an agent anticipate output.

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 schema provides 100% coverage of all 7 parameters with descriptions, so the baseline is 3. The description adds a high-level mention of 'filtering and pagination' but does not elaborate on individual parameters, leaving the schema to carry the detail.

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 specifies the verb 'Retrieve' and the resource 'previously computed analysis result using its token', making the tool's purpose clear. It distinctly differentiates from sibling tools like reactome_analyze_identifier (which computes new analyses) and export tools (which export results).

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 phrase 'previously computed analysis result' implies usage after an analysis has been run, but no explicit guidance is given on when to use this tool versus alternatives like export_analysis_csv or top_pathways. It does not state exclusions or alternatives, only a general context.

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