notify_read_notifications

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

Without annotations, the description carries the burden. It discloses that the tool reads from a log file and returns data, confirming it is a read operation. However, it does not mention side effects (likely none), required permissions, or behavior on missing file. The transparency is adequate but not rich.

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 a single, well-structured sentence that immediately conveys the core purpose. No extraneous words or fluff; it earns its place efficiently.

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?

Given the presence of an output schema, the description does not need to detail return values. However, it omits handling of edge cases (e.g., missing log file, empty results) and default behavior for optional parameters. It is minimally complete but leaves gaps.

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 description adds meaning to both parameters: 'n' (number of notifications) and 'path' (log file path), which are otherwise undocumented (0% schema coverage). It clarifies the tool's function beyond the schema, though default behaviors for null values are not explained.

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 the action 'Return the last N notifications from the log file as a JSON array.' It specifies the resource (notifications from log file) and the result format (JSON array), distinguishing it from sibling notification tools that send or trigger notifications.

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?

While the description implies use for reading notifications, it does not explicitly state when to use this tool over alternatives (e.g., notify_notify for sending, notify_bell for a different notification type). No exclusions or contextual guidance are provided.

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