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

Goes well beyond the annotations by disclosing the ordering (newest first), the mutation trigger (mark_read=true marks returned items as read, consistent with readOnlyHint=false), the cross-tool side effect where get_status marks shown notifications as read, and the shape of the return value (type, text, timestamp).

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?

Three dense sentences, front-loaded with what it does and the default behavior, then the mutation caveat, then the return format and a usage cue. The parenthetical about get_status earns its space because it prevents double-reading.

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 no output schema, the description compensates by naming the return fields (type, text, timestamp). Together with the mutation and default-behavior notes, an agent has everything needed to call it correctly and interpret the result.

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%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the default unread behavior and the non-obvious get_status interplay that affects how unread_only should be set. The bearer fallback and limit range are left to the schema, which is appropriate.

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 (read), resource (notifications), scope (newest first), and enumerates the content types covered. It also distinguishes itself from get_status by explaining the interaction between the two, so an agent can tell them apart without opening either 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?

Explicitly tells the agent when to call it ('check it after place_orders or mission work'), explains the default unread behavior, and names the alternative path (pass unread_only=false) for re-reading notifications already consumed by get_status.

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