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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds the 50-item page cap, the owner-only authorization constraint, and a negative scope disclosure ('never manage credentials or raw Calendar access'). It omits return/pagination cursor format, keeping it from a 5.

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 short clauses, front-loaded with the core purpose, then pagination, then scope. Nothing is padded, though the trailing 'never manage credentials' clause reads as an afterthought rather than integral guidance.

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 2-param list tool with no output schema, the description tells the agent what the output contains (recipient details) and the archived default, which is reasonable. But with 0% schema coverage it should explain the cursor semantics (is 'after' an opaque token or a UUID?) and it does not.

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 both parameters are undocumented structurally, so the description carries the burden. It supplies the 'archived' default, but the cursor parameter is referenced as 'next_after' while the schema property is named 'after' – a naming mismatch that undermines the one piece of pagination guidance given.

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 and resource ('Read... a page of up to 50 bookings') with scoping ('owner-only'), which clearly separates it from get_booking, cancel_booking, and list_booking_followups. It does not name a sibling explicitly, so it falls just short of the 5 level.

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?

Gives an implied usage hint for pagination ('Continue with next_after') and a default ('archived defaults to false'), but never says when to choose this over get_booking or the followups list, and gives no exclusions. Adequate but clearly incomplete.

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