ga4_remove_property

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

With no annotations at all, the description carries the full behavioral burden. It does meaningful work by implying the operation only removes a saved configuration entry ("forget") and by ruling out env-var-backed properties, but it never states whether the underlying GA4 property is untouched, whether the action is reversible, or what happens when the name doesn't match.

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 short sentences, purpose front-loaded, with the constraint immediately after. No filler and nothing that could be trimmed without losing information.

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 one-parameter tool with no output schema and no annotations, the description covers the essentials: what it does and the one precondition that blocks it. The remaining gap is post-call behavior (idempotency, behavior on unknown names), which is minor at this complexity level.

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?

The single parameter has 100% schema description coverage ("Saved property name"), so the baseline is 3. The description adds nothing about matching rules, case sensitivity, or whether the name must correspond to an existing saved entry.

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?

"Forget a saved GA4 property" gives a specific verb (forget/remove) plus the exact resource, and the word "saved" scopes it to a locally stored property rather than the GA4 property itself, which distinguishes it from siblings like ga4_list_properties or ga4_property_details. It stops short of naming a sibling explicitly, so it lands at 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?

The description supplies one real when-not condition: properties sourced from environment variables cannot be removed here. It gives no when-to-use framing, no pointer to how to discover removable saved properties (e.g. ga4_list_properties), and no alternative for the env-var case, so usage is only implied.

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