List ModDB notifications

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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful context beyond that: it is scoped to the logged-in account's own notifications and the payload consists of notification events (comments, mentions, releases). It says nothing about pagination, ordering, volume limits, or whether unread state is returned, which matters for a notifications feed.

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, no filler, front-loaded with the scope and resource, then a single practical hint. Every sentence earns its place.

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 no-param, read-only list tool with no output schema, the description covers identity scope and the shape of the results, which is what an agent needs to select and call it. It stops short of describing pagination or result ordering, a minor gap for a feed-style endpoint.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description's mention of the account scope is the only relevant semantic note.

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?

Specific verb (List) plus resource (ModDB notifications) scoped to the logged-in account, with the notification kinds enumerated (comments, mentions, releases of followed mods). This lets an agent separate it from siblings like list_comments or list_my_mods without opening any 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?

The second sentence implies a workflow ('quickest way to find comments awaiting a reply on your mods'), which nudges the agent toward this tool over list_comments for that task. However, it never explicitly states when to use this versus mark_notifications_read or when not to use it, so usage is only implied.

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