Get form submissions

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful filtering and date-format context, but does not disclose pagination behavior, inclusive date semantics, or return shape; given the annotations, 3 is appropriate.

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?

Two sentences with no filler. The main action and scope are front-loaded, and the date-format sentence is necessary and placed second.

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 tool, the description plus schema provides enough to invoke it correctly: location scope, optional form filter, date range filter, date format, and pagination defaults. Missing response-shape details are not blockers for calling the tool correctly.

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?

The description adds meaning beyond the schema by framing formId and startAt/endAt as optional filter dimensions ('optionally filtered to one form or a date range'). It also reinforces the date format. Page and limit lack descriptions, but their names, defaults, and constraints make them self-explanatory.

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 a specific verb ('Fetch') and resource ('submissions for a location's forms'), and adds optional filters. This clearly distinguishes it from sibling tools like ghl_get_survey_submissions, ghl_list_forms, and ghl_list_surveys.

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 clearly states the use case: retrieving form submissions for a location, optionally narrowed by form or date range. It does not explicitly name alternatives, but the context is unambiguous and no exclusions are stated.

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