ga4_property_from_firebase

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

With no annotations, the description carries the burden and does well: it discloses required API enablement (firebase.googleapis.com on the quota project), required IAM role (Firebase Viewer/Lector), and that failures return actionable access errors. It stops short of stating whether it performs any writes or how large the response can get.

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 purpose and the 'use before ga4_configure' guidance are front-loaded, which is good. However the prerequisite sentence mixes languages ('Firebase Viewer (o Lector) en el proyecto de Firebase'), reducing clarity for an agent parsing requirements.

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 single-parameter lookup with no output schema, the description covers purpose, prerequisites, error behavior, and a related alternative. The main omission is a hint about the shape of the returned property/stream data, though the opening sentence partially implies 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?

There is a single parameter with 100% schema description coverage, so the schema already explains the project id format. The description adds no extra meaning about the parameter, which matches the baseline for full 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?

States a specific verb and resource ('Find the GA4 property linked to a Firebase project') plus the returned detail (data streams per Android/iOS app). It does not distinguish itself from similarly-named siblings like ga4_firebase_links or ga4_firebase_apps, which an agent could easily confuse it with.

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?

Explicitly says to use it before ga4_configure when only the Firebase project is known, and routes access-checking to ga4_check_access. This covers the main selection decision, though it doesn't rule out when not to use it versus the firebase/apps siblings.

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