Track a deep link open event

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

Annotations already declare this is a non-read-only, non-idempotent, destructive, open-world operation, but the description adds nothing to explain those traits. It does not mention the required `confirm` flag, the private `account` scoping, or why a 'tracking' call is flagged destructive, which is exactly the kind of context annotations cannot convey. The only extra fact is platform coverage (iOS and Android).

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?

A single, front-loaded sentence with no filler. It is appropriately sized, though the brevity is partly responsible for the behavioral and usage gaps rather than being a virtue of precision.

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?

With 100% schema coverage and annotations carrying the safety profile, the minimum needed to invoke the tool is present. However, for a destructive-flagged mutation requiring a `confirm` flag and private account scoping, the description leaves an agent without operational context on confirmation or the probabilistic-tracking fallback.

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 100%, so the deepLink/dubDomain fallback logic and the payload/payload_file exclusivity are already fully documented in the schema. The description contributes no additional parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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 ('track') and resource ('when a user opens your app via a Dub-powered deep link'), which is far clearer than the bare name. It implicitly distinguishes itself from sibling trackers like track_lead and track_sale by scoping to deep-link open events, though it never names those siblings explicitly.

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?

There is no guidance on when to call this versus the other tracking endpoints (track_lead, track_sale) or when the deepLink vs dubDomain fallback path should be chosen. The 'when' is only inferable from the resource being tracked.

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