calendars_find_event_notification

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

The annotations (readOnlyHint, idempotentHint, destructiveHint false) already disclose the safety profile, but the description adds nothing beyond the literal 'Get notification'. It does not explain what constitutes a notification, whether it returns a single entity or list, or any side effects. Since the description carries the burden of behavioral context beyond annotations and fails to add any, this is a minimal score.

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 extremely short, but this reflects under-specification rather than efficient conciseness. It front-loads only the bare verb and noun without any supporting detail. The lack of structure or elaboration makes it impossible for an agent to act correctly, so it scores low on this dimension.

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 two required parameters, no output schema, and no parameter descriptions, the description is completely inadequate. It provides no information about the return value, expected behavior, or how parameters interrelate. This tool is unusable by an AI agent without external knowledge, so contextual completeness is essentially absent.

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 0%, so the description must compensate by explaining the parameters. It does not mention calendarId or notificationId at all, leaving their meaning, format, or relationship entirely unexplained. With no enums or additional schema details, an agent has no way to correctly populate these required fields.

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 notification' states a verb and a resource, but it is ambiguous and fails to differentiate from the sibling tool 'calendars_get_event_notification'. The name suggests 'find' while the description says 'get', and no context is given about what a notification is in this domain. This is barely more specific than a tautology and provides no meaningful purpose clarity.

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. With siblings like calendars_get_event_notification, calendars_create_event_notification, and calendars_update_event_notification, the description offers no context about the appropriate scenario, prerequisites, or differences from other tools. An agent has no basis to choose this tool over similar ones.

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