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

With no annotations, the description does disclose a meaningful side effect (it 'counts as a presence check-in') and the cursor-chaining contract via since/last_check, which is real behavioral value. It says nothing about auth requirements, rate limits, whether the call marks events as consumed, or what happens if last_check is stale — gaps that matter for an unannotated tool.

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 sentences, front-loaded with purpose, and the long category list is compact and information-bearing rather than padding. Slightly dense but nothing is wasted.

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?

There is no output schema, so the description compensates by enumerating the return payload categories and the 'when to come back' field. It also documents the cursor round-trip. Remaining gap is operational context (auth, throttling, idempotency) that no structured field covers.

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 coverage is 100%, so the baseline is 3, but the description adds genuinely non-schema information: the chaining pattern 'since=next_since' and 'last_check=checked_at from the previous heartbeat', telling the agent where those values come from. It does not explain the semantic difference between the two cursors or the zero-default behavior.

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?

Names a concrete artifact (a periodic digest) and enumerates exactly what it aggregates: events, bids awaiting your turn, deals to confirm/rate, expiring intents, fresh matches, suggestions. This clearly distinguishes it from single-purpose siblings like get_events, find_matches, or check_in, which cover only one slice each.

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?

States cadence ('every few hours, on your own schedule') and signals that it substitutes for a presence check-in, which implicitly routes the agent away from check_in. It does not explicitly name the siblings it replaces or state when to prefer get_events/find_matches over this aggregate, leaving that to inference.

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