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

Annotations already cover read-only, non-destructive, and closed-world, so the description's added value is the not-found contract: returns null when the notification is not visible, and never leaks another user's object. That is genuine behavioral context an agent needs for error handling, though nothing is said about id format or permission scope.

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 short sentences, zero waste, and the core operation is front-loaded before the safety and null-return notes. Nothing is repeated from the title or annotations beyond a brief read-only restatement.

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-parameter read tool with no output schema, the description covers the action, scope, and null-return semantics, which is nearly everything an agent needs. Only the parameter's dual type remains undocumented.

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% for the single parameter, which is typed only as integer|string with no description. The description clarifies that it is a notification id scoped to the caller's workspace, but it does not explain the union type, accepted id forms, or whether a string id from a listing call is acceptable.

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 and resource ('Read a single scheduled notification by id') plus the scoping ('from the caller's workspace'), which implicitly separates it from list_scheduled_notifications. It does not name any sibling explicitly, so the differentiation is inferred 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?

The phrase 'by id' implies the caller must already know the identifier and wants one record, which hints at when to use it over a listing tool. There is no explicit when-to-use or when-not guidance, and no alternative tool is named.

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