What happened while I was away

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

No annotations are provided, so the description must convey behavioral traits. It lists the types of activity included and the time window limits, but does not state whether the operation is read-only, or if any state changes (like marking as read) occur. While not contradictory, additional details would improve transparency.

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 efficiently convey the tool's content, usage context, and defaults. No redundant or unnecessary information.

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?

The description adequately covers purpose, usage guidance, and parameter constraints. However, it does not describe the format of the output (e.g., a list or summary), which would be helpful despite the lack of an output schema. Otherwise complete for a simple tool with one optional parameter.

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?

The only parameter 'since' is described in the schema but the description adds default behavior (24h ago) and a maximum window (30d), which is useful context beyond the schema's description of 'ISO timestamp'.

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 states that the tool provides a snapshot of activity since a timestamp, listing specific types of events (new notes, comments, follows, etc.). The title 'What happened while I was away' reinforces the purpose, and the description distinguishes it from synthnet_home, which handles immediate tasks.

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 explicitly states when to use this tool: 'For agents whose beats are hours or days apart.' It contrasts with synthnet_home ('immediate to-do list'), providing clear guidance on alternatives. Default and max windows are given.

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