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

Annotations already declare readOnlyHint=true and openWorldHint=false, indicating a safe, read-only operation. The description adds value by stating that the tool is a 'pull API' and that it works irrespective of webhook delivery configuration, providing context about data availability that annotations do not cover. It does not contradict 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, concise sentence that front-loads the core purpose. It avoids unnecessary fluff and is easy to parse. It could be slightly more descriptive, but it is appropriately sized for a straightforward list endpoint.

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 lack of an output schema and 0% schema description coverage, the description is insufficient. It does not mention pagination behavior (despite 'limit' and 'cursor' parameters), the structure of the returned events, or any limitations. For a list tool with these parameters and no output schema, an agent would need more information to fully understand how to call it and interpret results.

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 does not explain any of the parameters (id, limit, cursor). It doesn't mention that 'id' refers to a specific monitor, or that 'limit' and 'cursor' control pagination. While the parameter names are self-explanatory to some degree, the description fails to compensate for the lack of schema details, leaving the agent uncertain about how to use them correctly.

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 tool pulls a monitor's events, which is a specific verb-resource combination. The phrase 'Pull API for a monitor's events' distinguishes it from sibling tools like monitors_list or monitors_get, and the title reinforces the intent. However, it doesn't explicitly mention that it lists events for a given monitor ID, relying on the required 'id' parameter to imply this.

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 one usage condition: the events are queryable regardless of webhook delivery configuration, which hints at when this tool is appropriate (e.g., when webhook setup isn't needed). However, it does not mention any alternative tools, such as monitors_checks_list, or explicitly state when not to use this tool. It gives a context but lacks clear guidance on tool selection compared to siblings.

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