ga4_delete_property

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

With no annotations, the description carries full burden. It discloses the soft-delete nature, recoverability window, and eventual permanent removal, plus prerequisites. It could mention side effects on associated data, but the given details are sufficient for agent understanding.

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 short and front-loaded, conveying the action and key details in one sentence plus additional notes. It is efficient but could have better structure (e.g., separate lines for 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 simple tool with 2 params and no output schema, the description covers purpose, behavior, and requirements comprehensively. Minor gaps: no mention of error conditions or confirmation behavior beyond being required.

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 50% (property described, confirm not). The description adds meaning by requiring confirm=true, implying it's a safety flag. However, it does not enhance property description beyond the schema's example. Given low coverage, description partially compensates.

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 the action ('Soft-delete (trash) a GA4 property') with a specific verb and resource. It distinguishes from sibling delete tools by focusing on property, and adds details about recoverability and permanent removal.

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 lists prerequisites ('Requires GA4_MCP_ENABLE_DELETES=true and confirm=true'), providing clear context for when to use. However, it does not explicitly state when not to use or mention alternatives, though none exist directly among siblings.

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