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

With no annotations provided, the description carries the full disclosure burden. It does well by listing the returned content categories and describing the incremental cursor contract, plus promising a 'when to come back' value. It does not explicitly state that the call is read-only or how authentication is handled, but the check-in framing and cursor language make the passive, stateful behavior evident.

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?

The description front-loads the purpose ('Your periodic check-in') and compresses a useful list of returned items into one information-dense sentence. It is slightly run-on, but every element contributes and there is no filler.

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?

Because there is no output schema, the description compensates by enumerating the expected returned content and by explaining how to advance cursors across calls. It is complete enough for routine polling, though the exact response shape and api_key transport details are left to the input schema rather than the description.

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 schema already documents each parameter. The description adds valuable inter-parameter semantics by linking since to next_since and last_check to checked_at from the previous heartbeat response, which helps the agent understand how the parameters work together rather than just their individual types.

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 clearly identifies the tool as 'Your periodic check-in' and enumerates exactly what it aggregates: new events, bids, deals, expiring intents, and fresh matches. It is clear about the resource and the action, but it does not explicitly contrast itself with siblings like get_events or find_matches, so differentiation is implied rather than named.

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 states a clear cadence ('every few hours, on your own schedule') and instructs the agent to pass since=next_since and last_check=checked_at from the previous heartbeat. This gives clear when-to-use context, but it does not spell out when not to use it or which sibling tool to prefer for narrower queries.

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