ghl_calendar_update

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

Annotations already provide idempotentHint, readOnlyHint, and destructiveHint, so the description's additional endpoint and OAuth scope details are helpful but not critical. No behavioral contradictions or new disclosures beyond 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?

Three concise sentences: title, action, endpoint, OAuth scopes. No redundant information. Front-loaded with the core purpose.

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?

Despite the complex schema with many nested objects, the description does not clarify update behavior (e.g., partial vs full replace), return type, or prerequisites. No output schema exists, but description omits any mention of response. Incomplete for a tool of this complexity.

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?

Input schema has 100% coverage with descriptions for all properties, including examples and enums. The description only notes 'Request body (schema carried verbatim...)' which adds no semantic value. Baseline 3 is appropriate since schema does the heavy lifting.

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 'Update Calendar' and 'Update calendar by ID', which is a specific verb+resource combination. It distinguishes from sibling tools like create, get, delete, and list by focusing on the update operation.

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 on when to use this tool versus alternatives such as ghl_calendar_create or ghl_calendar_get. The description only provides the endpoint and OAuth scopes, without contextual usage advice or prerequisites.

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