set_utm_params

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

No annotations are provided, so the description must convey behavioral traits. It states that parameters are 'automatically appended to the target URL on every scan redirect' and that setting 'clear' to true removes all UTM parameters. However, it does not clarify whether setting a new value overwrites an existing one or if there are any side effects, leaving some ambiguity.

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 three sentences long, front-loaded with the main action, and uses clear language. It is concise but still covers key points. Slightly more detail on overwrite behavior could be added, but overall efficient.

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 7 parameters and no output schema, the description adequately explains the core functionality: setting and clearing UTM parameters on redirect. It does not mention return values, but the schema implies success/failure (likely a confirmation). Given the tool's specificity, this is sufficient.

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?

The input schema has 100% description coverage, with each parameter clearly described (e.g., 'utm_source value (e.g. 'flyer', 'email', 'poster')'). The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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's purpose: 'Set UTM tracking parameters on a URL QR code.' It specifies the resource (URL QR code) and action (set UTM params), distinguishing it from siblings like 'update_qr_destination' which changes the target URL itself.

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 explains when to use the tool: 'to track QR code scans in Google Analytics or other analytics tools.' It does not explicitly state when not to use it or provide alternatives, but the context is sufficient for an agent to decide.

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