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

The annotations already declare read-only, non-destructive, open-world behavior, so the description does not need to repeat the safety profile. It adds useful context beyond the annotations: the result set is paged with a next_page token, the returned fields include id+name for linked entities, and the underlying call is GET /events. It still omits auth/permission requirements, but that is a modest gap given the annotation coverage.

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 sentences with no waste: the primary purpose and return fields come first, then the pagination instruction, then the HTTP verb/path. Every sentence earns its place and the most important information is front-loaded.

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?

With no output schema, the description usefully summarizes the returned fields and clarifies that linked entities are id-and-name only, which an agent needs to interpret results. It also covers the pagination contract. Minor omissions (e.g., no mention of default page size or empty-result behavior) keep it from a 5.

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 100%, so each of the nine parameters is already fully documented in the schema, and the description only implicitly references the time-window filters (starts_after/starts_before) without adding syntax or edge-case detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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 gives a specific verb ("List") and a concrete resource ("calendar appointments (Termine, e.g. viewings)"), and even enumerates the returned fields (title, place, start/end, state, linked contact/property/project). It does not explicitly differentiate itself from the closely named sibling propstack_list_activities, so it stops short of a 5.

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?

It states the tool operates "in a time window" and gives pagination guidance ("follow next_page"), which implies when it is used. However, it never names an alternative or exclusion condition (e.g., how it differs from propstack_list_activities or when to prefer a single-event lookup), leaving the user to infer routing.

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