surveymonkey_list_questions

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

No annotations are provided, so the description carries the full burden. It clearly indicates a read-only listing operation by using 'Lists', and it exposes pagination defaults. However, it does not disclose API limits, whether the response is paginated across questions or pages, or how the page_id relates to the pagination page parameter.

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 concise and front-loaded, leading with the core purpose and then listing arguments without fluff. It uses a clear structured Args block, though the per-parameter descriptions could add more value without making the text significantly longer.

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?

An output schema exists, so return-value documentation is not required, but the description still leaves a key conceptual gap: how page_id is obtained, how pagination interacts with the survey page, and whether the call lists all questions on that page. The ambiguity between the two 'page' meanings is a real usability gap for an AI agent.

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 0%, so the description must compensate for all parameter meaning. It gives one-line definitions for all four parameters, but they largely restate the parameter names. The distinction between 'Page ID' and 'Page number for pagination' is confusing, and the description does not clarify that page_id refers to a survey page while page refers to result pagination.

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 'Lists questions on a specific page of a survey' with a clear verb, resource, and scoping qualifier. It clearly differentiates from sibling tools like get_question (single question), create_question, and update_question by describing a list operation. The only minor ambiguity is between page_id and pagination page, but the core purpose is unambiguous.

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 guidance is given about when to use this tool versus alternatives such as list_pages, get_survey_details, or get_question. There are no exclusions or conditions to help an agent choose this over a sibling. The agent must infer usage purely from the name and one-line description.

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