Exports running Firestore, Auth, and Storage emulator data to a destination directory outside the project for backup or transfer.
Export the running Firestore, Auth and Storage data to a directory outside the project (firenook emulators:export).
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Destination directory | |
| force | No | Overwrite a non-empty foreign directory |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It states that the data is 'running' and exported outside the project, but does not disclose the filesystem write effect, overwrite behavior when the destination is non-empty, prerequisites such as the emulator being active, or failure conditions.
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 wording. The parenthetical command alias is compact and does not obscure the core action.
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 two-parameter export tool with full schema coverage and no output schema, the description is adequate to identify the operation and destination. However, with no annotations, it should say more about the write/overwrite behavior and any prerequisites to be complete for safe invocation.
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 description coverage is 100%, so both parameters are already documented. The description adds the useful context that the destination is outside the project, but it does not add meaning beyond the schema for the 'force' parameter or the overwrite/foreign-directory semantics.
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 names the resources ('Firestore, Auth and Storage data') plus the destination scope ('a directory outside the project'). It clearly distinguishes the operation from read/query siblings, but it does not explicitly contrast with the closest sibling, emulators_clear.
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 usage by saying it exports running emulator data to an external directory, which suggests backup or migration scenarios. It gives no explicit when-to-use/when-not-to-use guidance and never mentions emulators_clear or other alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.