ghl_survey_list

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

Annotations already declare readOnlyHint and idempotentHint. The description adds that it's a GET endpoint with surveys.readonly scope and requires pagination, providing some additional behavioral context beyond the boolean hints.

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 with three clear lines. It front-loads the purpose and provides essential technical details without excess verbiage, though it lacks a more organized 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?

Missing important context: no explanation of what surveys are, what the 'type' parameter does, that locationId is required, or the output format. It does not differentiate from ghl_survey_get_submissions, leaving gaps 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 low (25%, only limit has a description). The description only mentions pagination params (skip, limit) but does not explain 'type' or 'locationId', which are undocumented in the schema. It adds some value for pagination but insufficient overall.

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 starts with 'Get Surveys', which clearly indicates the action and resource. It adds endpoint details and OAuth scopes, distinguishing it from siblings like ghl_survey_get_submissions.

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 on when to use this tool versus alternatives. It mentions pagination but does not explain when to use this over other survey-related tools or provide use cases.

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