reactome_export_analysis_csv

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

With no annotations, the description carries the full burden of behavioral disclosure. It says only 'Export analysis results as CSV files,' which does not clarify whether the operation is read-only, returns a download or inline content, or has any side effects. No details on output format, file size limits, or error behavior are given. This is insufficient for a tool with no annotations.

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 one concise sentence, front-loaded with the action and resource. It contains no filler or redundancy, earning a perfect score for conciseness.

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 schema covers all parameter details, and the description confirms the output format. However, there is no output schema, no annotations, and no explanation of how the CSV is returned (e.g., file download, string). The tool is minimally invocable with the schema, but lacks contextual depth for an agent to fully understand expectations.

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 provides 100% coverage of parameter descriptions, including the enum for 'type' and the default for 'resource'. Since the schema already explains each parameter, the description adds no extra semantic value. The baseline of 3 is appropriate given complete schema coverage.

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 the action ('Export') and the resource ('analysis results as CSV files'). It distinguishes this tool from sibling export tools like export_sbgn, export_sbml, and export_json by specifying CSV format. The verb and resource are specific and immediately understood.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., JSON export or analysis result viewers). There is no mention of prerequisites, context, or exclusions. The description merely states what it does, leaving the agent to infer usage from the name and schema.

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