ghl_calendar_block_slot_create

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

Annotations already indicate this is a mutation (readOnlyHint=false). The description adds OAuth scopes and endpoint info, which provide some auth-related insight. However, it does not explain side effects (e.g., does this create a time block that prevents appointments?), so behavioral understanding remains limited.

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 very short but contains redundancy (title repeated twice). It efficiently conveys the endpoint and scopes, but the repetition wastes space. It is acceptable but not well-structured.

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?

Given the tool has 7 parameters (nested) and no output schema, the description lacks essential context. It does not explain the purpose of block slots versus regular events, nor what the response contains. The description is insufficient for an agent to fully understand the tool's role.

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 input schema has 100% description coverage, so all parameters are documented. The tool description itself does not add any parameter-level meaning beyond what the schema provides, but the schema is sufficient. Baseline 3.

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 the verb 'Create' and the resource 'Block Slot', so the tool's action is identifiable. However, it does not explain what a block slot is, which could help distinguish it from other calendar tools like event creation. It is a specific verb+resource pair, meriting a 4.

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_calendar_block_slot_update or other calendar event tools. The description provides no context for selection, only the endpoint and OAuth scopes.

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