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

With no annotations, the description bears the full disclosure burden. It adds real value by stating the auth requirement and the privacy guarantee ('Event records never contain customer payloads'), but leaves key behaviors unstated: the retention window implied by 'recent', ordering, pagination vs the limit cap of 100, and whether the 'one-time' token is consumed or reusable on repeat calls.

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?

Three tight sentences, front-loaded with what is returned, then the auth requirement, then the privacy caveat. No filler and every sentence adds information.

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?

No annotations and no output schema mean the description is the sole source of behavioral detail, and it does cover the returned event kinds and payload-exclusion guarantee. However, it omits the semantics of limit/operationId and the recency window, which matter for a history-retrieval tool.

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% across 4 parameters, so the description must compensate. It only touches monitorId and monitorToken (adding the useful 'one-time' qualifier) and says nothing about limit or operationId, leaving half the parameters undocumented anywhere.

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?

States a specific verb ('Retrieve') and resource ('recent event timeline for a private monitor') and even enumerates the event categories returned (creation, stale transitions, recovery, blocked checks, revocation). That is enough for an agent to tell it apart from monitor_status or monitor_revoke by scope, though no sibling is named explicitly.

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 carries the credential prerequisite ('Requires its monitor ID and one-time monitor token') and implies an audit/history use case via 'recent event timeline', but never says when to choose this over monitor_status or contract_history, and gives no when-not guidance.

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