Mark notifications read

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

Adds real information beyond the annotations: the blast radius is limited to 'this account's notifications' and the call needs no user confirmation, which explains the destructive/readOnly posture in practical terms. It also describes the observable effect ('clears the unread count on the bell'), though it does not address whether a missing group name errors or silently no-ops.

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, front-loaded with the action and scope, then the effect and safety note. Nothing is redundant with the title and every clause carries information.

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 one-optional-parameter mutation with annotations and no output schema, the description covers scope, effect, and confirmation behavior adequately. Only the failure mode for an unknown group name is left unstated.

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 the schema already documents the group parameter as 'URL name' with a default of all groups. The description restates the same all-vs-one choice without adding format or edge-case detail, so the schema is doing the heavy lifting — baseline 3.

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 specific verb (mark read) applied to a specific resource (your notifications) with an explicit scope choice: 'everywhere or in one group.' The verb alone separates it from list_notifications and the many group/post management siblings, so the agent can route without opening a 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?

Gives clear conditional guidance on the only real decision point — whole-account versus single-group scope — and notes it 'runs without asking first,' which tells the agent not to request confirmation. It stops short of naming an alternative tool or a when-not-to-use condition, so it is clear but not fully complete.

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