ghl_get_form_submissions

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

With no annotations, the description carries the full transparency burden. It discloses the query scope (specific or all forms) and implies a read-only operation via 'Get'. However, it does not describe pagination, response format, or other potential behavioral nuances.

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 a single clear sentence with no redundant information, making it highly concise and well-structured.

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?

The tool has five parameters and no output schema or annotations, but the description gives enough context for a basic understanding. It lacks details on pagination, return structure, or any edge cases, which would improve completeness for a more complex tool.

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 to formId by explaining 'specific form or all forms', which complements the schema. However, the page and limit parameters are undocumented in both the schema and the description, and the coverage of 60% is only partially compensated.

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 clearly states the tool retrieves form submissions, with an optional filter by form. It distinguishes from sibling tools like ghl_get_survey_submissions and ghl_get_forms by specifying 'submissions' and 'forms'.

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 provides clear context: use this tool to get submissions for a specific form (by formId) or all forms in the location. It does not explicitly mention alternatives, but the scope is well-defined and implies when it is appropriate.

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