Get GHL Calendar

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read. The description adds no extra behavioral context such as return format, rate limits, auth requirements, or behavior when the calendar ID is invalid. It is neutral but uninformative beyond the annotations.

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 that directly states the tool's function without unnecessary words. It is front-loaded and 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?

The tool is simple with one parameter and annotations, but there is no output schema. The description does not explain what 'details' include or what to expect in the response, nor does it indicate any caveats. It is minimally viable but lacks contextual richness for a get operation.

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%, with calendarId described as 'Calendar ID'. The tool description adds no additional meaning about the parameter, but the schema already provides sufficient semantic coverage, so 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 'Get details of a specific calendar' uses a specific verb ('Get') and resource ('specific calendar'), clearly indicating it fetches one calendar rather than listing them. It distinguishes from sibling ghl_list_calendars by emphasizing 'specific', though it does not explicitly mention using the calendarId.

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?

There is no guidance on when to use this tool versus alternatives like ghl_list_calendars. It does not state prerequisites, exclusions, or scenarios where the list variant would be preferred. The description offers no usage context beyond the basic action.

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