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

Goes well beyond the annotations by disclosing two non-obvious behaviors: "reading marks nothing as read" (the annotations only say read-only, not that unread state is preserved) and a 180-day retention cutoff that affects what can be returned. It also surfaces that the reply carries an unread count, which matters for how an agent reports results.

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?

Front-loads the core action and keeps to a few dense sentences with no filler. Mild redundancy in enumerating per-notification fields (kind, title, body, link, day, unread) that the output schema already defines, which costs it the top score.

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?

With annotations carrying the safety profile and an output schema carrying the return shape, the description covers everything else an agent needs: content kinds, ordering, non-mutating read semantics, retention limits, and the unread count. Nothing material is missing.

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% and both parameters (limit with 1-20 bounds and default 10, unread_only defaulting false) are fully documented in the schema. The description adds nothing to either parameter beyond restating the newest-first ordering, so the baseline 3 applies.

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?

States a precise verb and resource ("Reads the user's Forkmate notifications") plus the ordering ("newest first") and enumerates the three kinds of content returned. No sibling tool deals with notifications, so the agent can route unambiguously without opening the schema.

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?

Usage is only implied: the description says what notification kinds exist, which hints at when it is useful (checking fixes, release notes, account messages), but it never states a when-to-use condition or any exclusion, and points to no alternative. Adequate but not explicit.

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