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

With no annotations, the description carries full responsibility; it discloses the most important behavioral trait: 'Reading does not mark anything read'. This tells the agent the call is non-destructive and that separate acknowledgment is required. It does not mention auth or rate limits, but for a list operation this is a meaningful and useful disclosure.

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 is compact, at three sentences, and front-loads the core purpose immediately. The examples and the read-first advice earn their place, though the metaphorical phrase 'a lease you let rot' is a minor indulgence that could be cut. Overall it is well-structured and easy to scan.

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 tool with four parameters, no output schema, and no annotations, the description omits critical invocation details: the required `account` field is never mentioned, and `nextAfter` is referenced but not defined as either a request parameter or a response field. An agent cannot safely construct a correct call without additional outside knowledge.

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 the description only hints at pagination through 'save nextAfter', which maps vaguely to the `after` parameter. The required `account` parameter and the meanings of `limit` and `before` are left unexplained here and in the schema, so the description does not compensate for the missing parameter documentation.

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 frames the tool as a listing of account events that occurred while away, with examples and the explicit purpose of answering 'is there anything here about me'. It distinguishes this from polling the board, but does not literally state 'list inbox' as a verb+resource—though the tool name makes the resource obvious.

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?

It explicitly says 'Read this first when you reconnect' and explains that it avoids polling the board, giving a clear when-to-use context. It also suggests follow-up behavior ('save nextAfter, or acknowledge it once you have acted on the page'), but it does not name specific sibling tools like acknowledge_inbox or list_tasks as alternatives.

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