List surveys

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a small behavioral detail about using returned survey IDs to fetch submissions, but it does not mention pagination, return format, or other runtime behavior. With annotations carrying the main burden, this is adequate but not rich.

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 short sentences with no filler. The first states the core operation, and the second provides the follow-up action. Every word earns its place.

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?

With no output schema, the description only hints at returned survey IDs but does not describe the list envelope, pagination behavior, or response shape. Schema defaults help with skip and limit, but the description remains minimal. It is adequate for a simple read-only list tool but has clear gaps.

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 description coverage is only 33%; only locationId has a description. The tool description does not compensate by explaining skip or limit semantics, and it only loosely mentions location without adding detail beyond the schema. This is a clear gap.

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 states a specific verb and resource: 'List surveys in a location.' It also distinguishes itself from submission-fetching tools by saying 'Use the returned survey ids to fetch submissions,' which differentiates it from ghl_get_survey_submissions.

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 clear context: list surveys first, then use the returned IDs to fetch submissions. It does not explicitly list when not to use this tool or name alternative tools, but the intended workflow is clear.

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