Create Click

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

Annotations already indicate readOnlyHint=false, meaning mutation. The description adds 'manually track a click event' but no further behavioral details (e.g., idempotency, permissions, side effects). Since annotations carry the safety profile, the description contributes minimal extra transparency.

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 sentences, front-loaded with purpose and usage scenario. No wasted words, every sentence is informative.

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?

Despite 15 parameters, the description is minimal and does not mention return values or success behavior. There is no output schema to compensate. For a creation tool, missing response details is a gap. Adequate but not comprehensive.

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 each parameter having a description. The description does not add semantic value beyond the schema; it only states the required parameter (referrerUrl). Baseline of 3 is appropriate as the schema already explains parameters.

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 tool creates a click event for attribution purposes, with a specific verb ('create') and resource ('click event'). It distinguishes from sibling tools by specifying manual tracking for cases not automatically captured.

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 says 'Use when you need to create a click record that was not automatically tracked', providing clear context. It does not explicitly mention when not to use or alternatives, but the context is strong enough to differentiate from automatic tracking.

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