calendars_get_event_notification

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety aspects. However, the description adds no behavioral context beyond these, such as pagination, filtering, or response format. It neither contradicts nor enriches 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 short phrase, but it is under-specified rather than efficiently concise. It provides no useful front-loaded information and reads as a minimal placeholder rather than a deliberate, informative summary.

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?

With 5 parameters, no output schema, and no explanation of return values, filtering semantics, or how notifications are populated, the description is wholly inadequate. An agent cannot correctly select or invoke this tool based on this information.

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 coverage is only 40% (skip and limit have descriptions, but deleted, isActive, and calendarId are undocumented). The description explains none of the parameters or their meanings. With coverage below 50%, the description needed to compensate but did not.

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 notifications' is vague and unspecific. It doesn't indicate these are event notifications nor distinguish this tool from similar siblings like calendars_find_event_notification or calendars_create_event_notification. It provides only a generic verb and noun with no resource context.

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. The description gives no context, prerequisites, or exclusions, leaving the agent without direction about when this tool is appropriate.

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