bootstrap_site_measurement

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

The description states that with apply=True the tool 'creates only the missing pieces' (GA4 property, stream, key events, dimensions), which is a write operation, while annotations declare readOnlyHint=true. An agent trusting the annotation could invoke apply=True believing the call is non-mutating. The description's own behavioral content is rich, but it directly contradicts the structured safety hint.

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?

Front-loads the plan-vs-apply distinction, which is the single most important fact, then covers safety, returns, and follow-ups before a clean Args list. It is longer than average, but the length is justified by an 8-parameter dual-mode tool; a little tightening around the repeated 'missing pieces / skipping what exists' phrasing is possible.

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 an open-world, potentially-mutating bootstrap tool this covers the mode switch, confirmation requirement, server prerequisite (--enable-writes), idempotency, and manual follow-up steps. An output schema exists, so it correctly does not need to narrate return structure beyond mentioning the G- measurement ID and TXT token.

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 description coverage is 0%, so the description must carry the parameter burden, and it does: every one of the eight args is documented with meaning, format, or example (site_url URL form, account_id cross-reference to list_account_summaries, IANA time_zone, ISO 4217 currency_code, key_events example, custom_dimensions, and apply's default 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?

States a specific verb and resource ('Plan, and optionally apply, the full measurement setup of a website') and immediately scopes its domain (GA4 property/stream, key events, custom dimensions, Search Console property). This is clearly distinguishable from sibling read-only lookups like list_properties or list_data_streams.

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?

Gives explicit when-to-use guidance: default apply=False produces a plan that must be shown to the user for confirmation before apply=True. It also names the alternatives for the parts it does not handle (sc_verify_site_dns, sc_submit_sitemap) and explains why they stay manual, so the agent knows exactly where this tool's job ends.

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