ghl_calendar_list_blocked_slots

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, signaling a safe read operation. The description adds that startTime/endTime are epoch milliseconds as strings and lists OAuth scopes, but does not disclose potential limits, pagination, or empty result behavior.

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 concise, with only a few lines covering the critical format note, endpoint, and scopes. It is front-loaded with the parameter format note, which aids understanding. Every sentence is useful.

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 return format, pagination, or what fields are included in the blocked slots list. For a list tool, this is a significant gap, making the description incomplete for the agent.

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%. The description adds value by clarifying that startTime and endTime are passed as strings, which supplements the schema's 'in millis' description. However, only two of six parameters are mentioned, and the schema already describes all parameters adequately.

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 Blocked Slots' and provides the endpoint, making it obvious that the tool retrieves blocked calendar slots. However, it does not differentiate from sibling tools like ghl_calendar_list_free_slots, missing explicit distinction.

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?

No guidance is given on when to use this tool versus alternatives such as ghl_calendar_list_free_slots or ghl_calendar_block_slot_create. The description lacks any when-to-use or when-not-to-use context.

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