List Forms questions

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description does add genuinely new context by disclosing the return shape (questions grouped into pages, wrapped in a {pages} envelope), which matters since no output schema exists, but it says nothing about pagination limits, ordering, or empty forms.

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?

A single front-loaded sentence fragment that delivers the key structural fact with zero waste. It is appropriately sized, though slightly terse for a description carrying some of the behavioral burden.

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 simple one-parameter read tool with rich annotations, this is close to adequate, and the {pages} envelope hint partially compensates for the missing output schema. However, it omits sibling routing and any pagination or ordering behavior, leaving gaps an agent would want filled.

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% and the single survey_id parameter is fully documented in the schema (24-char hex, sourced from surveys_list). The description adds nothing about the parameter, so the baseline 3 applies.

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 states the resource (a form's questions) and the organizing structure (grouped into pages), so an agent knows this is the read/list variant rather than the singular forms_questions_get or the mutating forms_questions_create. It is clear but never explicitly names the sibling it contrasts with, keeping it short of a 5.

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?

There is no when-to-use guidance and no mention of alternatives such as forms_questions_get for a single question. The agent must infer the read-only list role from the name and annotations alone.

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