firebase_setup

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

With no annotations, the description carries the full load. It discloses automatic execution, required tools (gcloud authed, firebase-tools), and side effects (creates GCP project, iOS app, plist), plus live event tracking. But it omits idempotency, reversibility, permission details beyond gcloud, and failure behavior—important for a setup mutation. Score 3.

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?

Two sentences with zero waste, front-loaded with the mandatory nature and the concrete outputs. Arrow notation efficiently communicates the artifact flow.

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 description explains the tool's purpose, mandatory nature, and prerequisites, but with 0% parameter schema coverage it leaves the agent without crucial input guidance (what each argument should contain, what approval_id is for). No annotations compound the gap. Adequate only for high-level understanding, not for correct 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?

Schema coverage is 0% with 4 parameters; the description provides no mapping or meaning for app_dir, bundle_id, app_name, or approval_id. The agent must guess parameter intent entirely, a severe 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?

States a specific verb+resource ('Set up Firebase Analytics') and enumerates the concrete artifacts it creates (GCP project, iOS app, GoogleService-Info.plist). However, it does not explicitly distinguish itself from the many sibling setup_* tools (e.g., setup_services, setup_set), so 4 rather than 5.

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?

Marks the tool as 'MANDATORY for every app' and gives prerequisites ('gcloud authed + firebase-tools'), providing clear context for when to use it. It stops short of naming when-not-to-use or alternatives, so 4 is appropriate.

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