form_report

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds a specific operational constraint: rate limited to 2/min. It also discloses the primary return contents (views, submissions, submit rate), providing useful behavioral context beyond the structured annotations.

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 a single, front-loaded sentence that conveys the tool's purpose, the key metrics, and the rate limit without wasted words. It is appropriately sized for the tool's complexity.

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?

Given the rich schema descriptions, read-only annotations, and simple aggregate output, the description covers the essential return values and rate limiting. It is missing only explicit routing guidance among the many sibling report tools, which keeps it just short of fully complete.

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 high at 83%, so parameters like start, end, year, quarter, and timeframe are already documented in the schema. The description adds no parameter-level meaning beyond identifying the account context, so the 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 identifies the resource (sign-up forms) and the metrics reported (views, submissions, submit rate), which distinguishes it from sibling report tools like campaign_report or flow_report by domain. However, it lacks an explicit verb and does not directly name or contrast itself with any sibling.

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 gives no guidance on when to use this tool versus alternatives such as campaign_report, flow_report, or segment_report. It does not state exclusions, prerequisites, or recommended scenarios beyond the generic 'for a Klaviyo account'.

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