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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new facts: the pagination contract via next_cursor, the shape of each returned answer (question, stored value, readable answer, hidden_fields link values, CRM contact) and that calls are free. Missing only rate limits or an explicit statement of what happens when no responses exist.

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 short clauses with the return shape first and the pagination rule second; nothing is padded. The opening is a noun fragment rather than a sentence, which slightly hurts front-loading clarity but costs no length.

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 usefully sketches the response record and the continuation token, which is the main thing an agent needs to loop pages correctly. It omits any guidance on the since/limit filters, which is the remaining gap for a four-parameter list tool.

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 75%, so most parameters are already documented, and the cursor description in the schema already says 'The next_cursor of the previous page' — the prose largely restates that. The limit and since filters are never mentioned in the description, so it adds little beyond the schema baseline.

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 the specific resource (a form's responses) and ordering (newest first), plus what each record contains. It is distinguishable from forms_get_response and forms_export_responses by implication of a paged list, though it never names the singular/export siblings.

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?

Gives one concrete usage rule — re-call with next_cursor when it is non-null — which tells the agent how to paginate. It does not say when to prefer this over forms_get_response (single response), forms_export_responses (bulk export) or forms_summary, so alternative selection is left to inference.

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