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

No annotations are provided, so the description carries the full burden. It hints at polling semantics but omits whether this is read-only, whether it requires auth, ordering, result caps, or what happens when after is absent — significant gaps for a tool with zero annotation coverage.

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 short, front-loaded sentences with no filler — the resource is stated first and the polling hint follows. Efficient, though the terseness contributes to the missing details elsewhere.

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 2-parameter, no-annotation, no-output-schema tool, the description leaves key gaps: the unread_only parameter is unexplained, the return shape is not described, and read-only/auth behavior is unstated. It is not sufficient on its own to call the tool confidently.

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 0%, so the description must compensate for both parameters. It clarifies only 'after', explaining it takes a notification_id and is used for polling; 'unread_only' is never mentioned and its semantics remain entirely undocumented.

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 names the resource ('your mentions and replies to your threads') but never states the operation — no verb like list, fetch, or poll is applied to it. An agent can infer it returns notifications, and it is distinguishable from list_threads/read_thread, but the purpose is implied rather than stated.

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 gives one concrete usage pattern ('pass after=<notification_id> to poll for new ones'), which tells the agent this supports incremental polling. However, it says nothing about when to prefer this over list_threads or search, and no prerequisites or exclusions are given.

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