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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the return shape ("{ pages, events }") and the underlying endpoint, but says nothing about pagination mechanics, the default window behavior if from/to are omitted, or rate limits — useful context beyond annotations but not rich.

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?

Two compact sentences with zero waste: the operation and its scope come first, followed by the return shape and endpoint. Nothing is padded or repetitive.

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 no output schema, the description usefully notes the response shape (pages, events), and the 100% schema coverage handles all filtering parameters. It is slightly thin on pagination flow and on what happens when from/to are omitted, but nothing an agent needs to invoke the tool is missing.

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 all eight parameters (tzid, from, to, calendar_ids, and the three filter booleans) are already documented in the schema. The description only restates the time-window concept and adds no format or default details beyond what the schema provides, so the baseline of 3 applies.

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 and resource ("Read events") plus the scope ("across the account's calendars over a time window"), which is clearly distinct from sibling tools like list_calendars or get_free_busy. It does not explicitly name or contrast with those siblings, so it falls short of the top band.

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?

There is no explicit when-to-use guidance and no mention of alternatives such as cronofy_get_free_busy for availability checks or cronofy_upsert_event for writes. The time-window scope hints at usage but the agent must infer when this tool is the right choice.

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