ghl_calendar_notification_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral context like OAuth scopes, endpoint, and pagination, but does not discuss rate limits or other traits. It is consistent with 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 concise with no unnecessary words. It front-loads the purpose and includes essential details (endpoint, scope, pagination). Could be slightly better structured (e.g., grouping param info), but overall efficient.

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 description lacks details about the response format, what constitutes a 'notification', and how the boolean filters (`deleted`, `isActive`) work. With no output schema, more context on return values is needed. The tool has 5 parameters and no output schema, so the description should provide more guidance.

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 only 40% (2 of 5 params documented). The description adds pagination guidance for `limit` and `skip` but leaves `deleted`, `isActive`, and `calendarId` unexplained. Description partially compensates but not sufficiently for the low coverage.

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 it returns calendar notifications based on a query, with the endpoint and pagination details. The purpose is clear, though it doesn't explicitly distinguish from the sibling `ghl_calendar_notification_get` which would retrieve a single notification.

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 mentions pagination for full result sets but does not provide guidance on when to use this tool versus alternatives like `ghl_calendar_notification_get`. No when-not-to-use or prerequisite information is given.

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