Get survey submissions

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

The readOnlyHint annotation already signals a safe read operation, and the 'Fetch' wording aligns with that. The description adds little beyond the annotations—it does not disclose pagination behavior, date-range semantics, or result ordering.

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 with an active verb and no filler. The optional filter is presented compactly without repeating parameter defaults.

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 list operation, the description states the essence and annotations cover safety, but an agent still lacks explicit guidance on pagination, date-range behavior, and whether omitting surveyId returns all submissions. Given six optional parameters and no output schema, more context would improve call correctness.

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 descriptions already cover startAt, endAt, and locationId, and constraints document page and limit. The description contributes meaning for surveyId by noting the optional filter, which compensates for the missing schema description, but it does not elaborate on how pagination or date filtering interacts.

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 uses the specific verb 'Fetch' and identifies a precise resource: survey submissions for a location. It clearly distinguishes this from sibling tools like ghl_get_form_submissions by naming 'surveys' as the scope, so an agent can tell them apart.

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?

The description implies this tool is for retrieving survey submissions and optionally filtering to a single survey, but it never states when to prefer this over siblings like ghl_get_form_submissions. No explicit alternatives or exclusion criteria are given.

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