ga4_delete_rollup_property_source_link

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

No annotations exist, so the description must disclose behavior. It correctly indicates this is a delete/remove action and highlights required safety flags. However, it does not mention irreversibility or permission requirements, which would be valuable for a destructive 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?

The description is a single sentence that immediately states the action and prerequisites. It is front-loaded with [GA4 DELETE] and wastes no words.

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 tool with 2 parameters and no output schema, the description adequately covers purpose and usage conditions. It could mention that the source property itself is not deleted, only the link, but the current text is sufficient for safe 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 100% with clear descriptions for both parameters (name URL format, confirm boolean). The description adds no extra semantic detail beyond the schema, so it earns the baseline score.

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 "Remove a source property from a rollup (360)" uses a specific verb and resource, clearly distinguishing it from siblings like ga4_delete_property or ga4_delete_firebase_link. The [GA4 DELETE] prefix further aids identification.

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 explicitly states prerequisites: requires GA4_MCP_ENABLE_DELETES=true and confirm=true. This gives clear conditions for use. However, it does not mention when not to use or suggest alternatives, such as using the create counterpart for adding a link instead.

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