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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds meaningful beyond-annotations context: form_views and response_rate are null until views are tracked (forward-only), and optional fields response_time_distribution and views_timeline are disclosed. No contradiction.

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 opens with a substantive purpose sentence, then provides a compact return shape and a useful edge-case note. The Args block is somewhat redundant with the schema but is short and scannable, so it does not significantly hurt structure.

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 read-only analytics tool with strong annotations and full schema coverage, the description gives the return shape and an important data-scarcity edge case. It could clarify what per-question stats contain or timeline granularity, but nothing essential is missing.

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 provides 100% coverage with descriptions for both parameters and a default for response_format. The description's Args block only restates form_id and response_format without adding extra meaning, so the schema carries the semantic burden.

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 ('get') and resource ('form analytics'), and enumerates the exact content: overview KPIs, responses-over-time timeline, and per-question stats. This clearly differentiates it from siblings like foxform_get_form or foxform_list_responses.

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?

No explicit when-to-use or alternative routing is provided. The word 'Aggregated' and the KPI list imply use when summary analytics are needed rather than raw responses, but an agent is not told to prefer this over foxform_export_responses or foxform_list_responses in any scenario.

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