ghl_get_surveys

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

With no annotations provided, the description carries the full burden of behavioral disclosure. Though 'List' implies a read-only operation, it does not mention pagination behavior, default ordering, response format, or any side effects, adding minimal context beyond the tool name.

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 concise sentence with no redundant words, and the main action is front-loaded. It is not bloated, though it may be under-specified for the tool's complexity, which is acceptable under the conciseness dimension.

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 tool with three parameters and no output schema or annotations, the description is insufficiently complete. It doesn't explain how skip and limit work, what 'type' filters, or what the returned data looks like, leaving an agent with significant ambiguity.

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 does not refer to any of the three parameters (skip, type, limit). Only the schema's 'type' parameter has a description, leaving skip and limit completely undocumented. With schema coverage at 33%, the description fails to compensate and adds no meaning to the parameters.

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 it lists all surveys created in the location, using the verb 'List' and specific resource 'surveys', which distinguishes it from sibling tools like ghl_get_survey_submissions that deal with survey submissions rather than surveys themselves.

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 gives no guidance on when to use this tool versus alternatives such as ghl_get_survey_submissions or ghl_get_forms, nor does it mention pagination or filtering context. It simply states the basic function without any contextual use cases or exclusions.

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