List Firebase web apps

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

With no annotations, the description carries the full behavioral burden and falls short: it does not disclose pagination behavior (despite a pageToken parameter), auth/scope requirements, result ordering, or what a response contains. It simply restates the operation.

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?

A single efficient sentence with the core operation front-loaded and no wasted words. It is appropriately sized for the claim it makes, though the claim itself is thin.

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 paginated list tool with no annotations and no output schema, the description is too sparse: it omits pagination semantics, auth context, and the relationship to sibling list tools. An agent cannot fully determine correct invocation from it.

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 50%: projectId is documented (defaults to GOOGLE_CLOUD_PROJECT), but pageToken has no schema description and no explanation in the description either. The description adds no parameter meaning, so it fails to compensate for the coverage gap.

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 states a specific verb ('Lists') and resource ('web apps') and adds a scoping clause ('registered under a Firebase project'). The 'web' qualifier implicitly separates it from firebase_list_ios_apps and firebase_list_android_apps. However, it does not explicitly name those siblings, so differentiation is inferred rather than stated.

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?

There is no guidance on when to use this tool versus alternatives such as firebase_list_ios_apps or firebase_list_projects, and no prerequisites or exclusions are mentioned. The single declarative sentence only implies usage.

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