calendar_stop_channel

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the effect ('stop receiving push notifications') but omits details about idempotency, error states, or side effects (e.g., what happens if the channel doesn't exist). This is minimal transparency.

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, efficient sentence that conveys the core action without superfluous words. It is front-loaded and easy to parse, though it could benefit from slightly more structure or context without becoming verbose.

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's simplicity (2 required params, no output schema, no annotations) and the presence of similar sibling tools, the description is insufficient. It lacks details on how to obtain the resourceId, expected outcomes, or error handling, leaving an agent without enough context to use it reliably.

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 100%, so both parameters are already described in the schema. The tool description does not add any additional meaning or context beyond the schema descriptions, so it meets the baseline for no added value.

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 uses a specific verb 'Stop' and clearly identifies the resource as 'push notifications for a watch channel'. It effectively distinguishes this tool from siblings like drive_stop_channel by implying it operates on a Calendar watch channel, consistent with the 'calendar_' prefix.

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 provides no guidance on when to use this tool versus alternatives such as drive_stop_channel or gmail_stop_watch. It does not mention prerequisites, conditions, or typical use cases, leaving the agent without context to differentiate.

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