reactome_export_fireworks

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states 'Export' but does not clarify whether this is a read-only fetch, what response format is returned (e.g., file download vs. URL), or any side effects. The minimal wording leaves important behavior unspecified.

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 redundant words. Every word contributes to identifying the tool's purpose without filler.

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 tool is simple (2 optional parameters, no output schema), so the description need not be extensive. However, it lacks contextual detail such as what the 'fireworks' diagram represents and how this differs from other export tools. It is minimally viable but leaves room for clearer context.

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 100%, with both 'format' and 'species' having their own descriptions in the schema. The tool description adds no extra parameter meaning beyond what the schema already provides, which matches the baseline for high 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 uses a specific verb ('Export') and clearly identifies the resource ('pathway overview (fireworks) diagram') and target ('for a species'). This distinguishes it from sibling export tools like reactome_export_diagram or reactome_export_sbml.

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 implies when to use this tool (for a species-level fireworks overview) but does not explicitly contrast it with alternatives such as reactome_export_diagram or reactome_export_sbgn. There is no mention of when not to use it.

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