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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond them: the auth-key semantics that change what data is visible, plus the underlying endpoint. It does not discuss pagination behavior, which the schema partly handles.

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?

Three tight sentences with no filler, front-loaded on what is listed before the key-scoping rule. The trailing 'GET /tracking/forms' is marginally redundant but serves as an API reference anchor.

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 no output schema, the description compensates by naming the fields returned (id, name, match behavior). Pagination is left to the schema, which handles it well, so an agent has what it needs to call this correctly.

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%, including the 'Agency key only' notes on account_id/profile_id, so the baseline is 3. The description restates that Agency-only filtering constraint but adds no format or interplay detail 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?

States a specific verb and resource ('List the web forms WhatConverts tracks') and even enumerates the returned fields (id, name, how the form and its submit are matched). No sibling tool covers web forms, so the scope is unambiguous against the leads/accounts/profiles listers.

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?

Explains the key-dependent usage model clearly: a Profile key returns its own profile's forms, while an Agency key may narrow by account_id/profile_id. It gives the condition for using the filter params, though it names no alternative tool or when-not-to-use case.

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