Firebase MCP Server

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

No annotations provided, so description carries full burden. Fails to disclose error behavior (what happens if path invalid/document missing), return value structure, or whether operation is read-only/safe. 'Get' implies retrieval but lacks explicit safety or side-effect disclosure.

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?

Extremely concise at five words. No wasted language. Front-loaded with verb and object. However, extreme brevity contributes to under-specification; one additional sentence covering error behavior or sibling distinction would improve utility without sacrificing clarity.

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?

Minimum viable for a single-parameter retrieval tool. Covers the basic operation but lacks critical contextual gaps given the server has multiple retrieval tools (list_documents, query_collection): no error handling documentation, no return value hints, and no selection guidance for the agent.

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 coverage is 100% with 'documentPath' well-documented including example. Description mentions 'by path' which aligns with the parameter, but adds no syntax rules, validation constraints, or format details beyond the schema.

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?

States specific verb ('Get'), resource ('document'), and scope ('single', 'by path'). Implicitly distinguishes from 'list_documents' via 'single', but does not explicitly differentiate from 'query_collection' or when path-based vs. query-based retrieval is appropriate.

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?

Provides no guidance on when to use this tool versus siblings like 'list_documents' or 'query_collection'. Does not mention prerequisites (e.g., authentication) or edge cases (e.g., document not found).

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