ghl_form_get_submissions

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds pagination info but does not contradict annotations. The added value is limited beyond the structured data.

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 short and includes key details like endpoint and OAuth scopes. However, the pagination note is somewhat vague ('pass them to page through full result sets'), slightly reducing clarity.

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?

No output schema is provided, and the description does not explain the structure of returned submissions. For a retrieval tool, this omission is significant, as the agent would need to know what fields are available.

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 coverage is high (86%), and the sample schema provides detailed descriptions for most parameters. The description only mentions pagination params generally, adding little beyond the schema. Baseline 3 is appropriate.

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 'Get Forms Submissions' and provides the endpoint, indicating retrieval of form submissions. However, it does not explicitly differentiate from sibling tools like 'ghl_form_list' or 'ghl_form_upload_custom_files', which could cause confusion.

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 mentions OAuth scopes and pagination but provides no guidance on when to use this tool versus alternatives. There is no distinction between querying submissions vs. listing forms or other related operations.

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