timetree_start_monitor

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

No annotations are provided, so the description carries the full burden of explaining behavioral side effects. It mentions 'background polling' and notification delivery, but does not disclose that this is a persistent, stateful operation, how to stop it, whether multiple monitors can overlap, or what cleanup is required. For a side-effect-producing tool, this is a significant gap.

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?

A single, front-loaded sentence with no filler. Every word contributes to the core purpose and notification behavior, and it is easy to scan.

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?

For a stateful background-monitoring tool with zero annotation coverage and no output schema, the description is too sparse. It omits critical operational ctx such as the required lifecycle (stopping the monitor), login prerequisites, and parameter semantics, making it incomplete for reliable invocation.

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%, and the description fails to mention either parameter. calendar_id and interval_seconds are not explained at all, so an agent cannot understand how to choose or interpret them. The description adds no value beyond the raw input schema, which itself provides no semantic explanation.

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 the action ('Start') and the resource/scope ('background polling for calendar changes'), making its purpose immediately understandable. It also distinguishes itself from sibling tools like timetree_stop_monitor and timetree_monitor_status by focusing on the start action.

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 gives clear context: use this tool to begin polling for calendar changes and receive them as MCP notifications. However, it does not explicitly state when not to use it, what prerequisites exist (e.g., being logged in), or how it relates to timetree_stop_monitor/timetree_monitor_status, leaving usage guidance mostly implied.

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