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

Beyond the readOnlyHint annotation, it discloses the Pro-account prerequisite and failure mode (UPGRADE_REQUIRED, including historical data), the all-time period behavior when dates are omitted, the semantics of totalEvents as pre-deduplication raw counts, and the unit ranges of rate metrics. That is substantial behavioral context the annotations do not carry.

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?

Front-loads the purpose and return summary, then layers constraints and edge cases. Dense but each sentence (units, all-time default, upgrade gating) carries information an agent needs; it is somewhat long but not padded.

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?

Since there is no output schema, the description supplies the response shape ({ formId, period, metrics, breakdown, totalEvents }), the meaning of totalEvents, and the upgrade error path. For a read-only analytics tool with 7 params this is complete enough to invoke 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 coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: it explains that omitting both from/to yields period { from: null, to: null } (all time), states that rate metrics are 0–100 and counts are integers, and clarifies totalEvents. These are non-obvious semantics not derivable from the schema alone.

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?

Opens with a specific verb+resource ('Get form analytics') and enumerates the exact metrics and breakdown dimensions returned. It names the sibling form_list as the way to obtain formId, so an agent can distinguish it from other form_* tools immediately.

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?

Explicitly routes the agent to form_list to find formId before calling, and flags the Pro-feature gating that returns UPGRADE_REQUIRED. It stops short of naming when-not-to-use alternatives, so it is clear context without full exclusion guidance.

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