ghl_get_calendars

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

With no annotations provided, the description's verb 'List' conveys a read-only behavior, but it does not disclose additional behavioral traits such as pagination, response format, or permission requirements. It is minimally transparent but lacks depth.

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, front-loaded sentence with no redundant words. It efficiently states the tool's purpose without unnecessary detail.

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 simple list tool with one optional parameter documented in the schema, the description is mostly complete. It does not mention the optional filter or return shape, but these are minor gaps given the simplicity and schema coverage.

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 100% for the single parameter 'groupId', so the baseline is 3. The description does not mention the groupId parameter at all, adding no semantic value beyond what the schema already provides.

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 'List all calendars in the GHL location' uses a specific verb ('List') and resource ('calendars') with a clear scope ('all'), which distinguishes it from sibling tools like ghl_get_calendar (singular). It clearly states what the tool does.

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 implies usage for retrieving all calendars, but does not explicitly state when to use this tool over alternatives like ghl_get_calendar or ghl_get_calendar_groups, nor does it mention any exclusions or prerequisites. Guidance is minimal and inferred.

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