ga4_delete_skadnetwork_conversion_value_schema

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

With no annotations, the description carries the full burden. It discloses that the action is destructive and requires specific prerequisites, but does not mention irreversibility, rate limits, or what happens after deletion. The behavioral traits are partially transparent.

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 extremely concise with one sentence and a requirement note, front-loaded with '[GA4 DELETE]' for quick identification. No unnecessary 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 simple delete operation with two parameters and no output schema, the description adequately covers prerequisites and purpose. It does not explain the concept of SKAdNetwork conversion value schema, but the name and sibling tools provide context.

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%, so the schema already documents both parameters. The description only adds redundancy by restating that confirm must be true, providing no additional value beyond the schema.

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 clearly states it deletes the SKAdNetwork conversion value schema with the verb 'Delete' and specific resource name, distinguishing it from sibling delete tools like ga4_delete_account or ga4_delete_property.

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 provides explicit prerequisites (GA4_MCP_ENABLE_DELETES=true and confirm=true) and implicitly tells when to use this tool for deleting SKAdNetwork schemas. It does not explicitly list alternatives, but the context of sibling tools with similar names is sufficient.

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