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

Annotations already declare readOnlyHint=true, so 'Read-only' is redundant, but the description adds genuine behavioral value: it scopes access to 'your own' (authorization boundary) and warns that 'provider acceptance is not proof that the person saw the notice,' a real semantic caveat about the returned status.

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?

Front-loads scope, then the core action, then a caveat. Efficient overall, though 'Read-only' duplicates the annotation and the leading parenthetical adds mild clutter before the substantive clause.

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 single-parameter read tool with annotations covering the safety profile, the description conveys the semantics of the returned status well. The main remaining gap is the origin of request_id, but otherwise nothing critical is missing.

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?

With a single request_id parameter at 0% schema description coverage, the description must compensate. It identifies the parameter as the notification's request_id key but doesn't state where to obtain it (e.g., from request_owner_artifact_notification) or its UUID format, leaving a gap.

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 precise verb and object: 'read delivery status of your own private meeting artifact notification by request_id.' The parenthetical '(not a shared project message)' distinguishes it from shared-notice siblings like list_shared_notices. It doesn't explicitly name its create-side sibling request_owner_artifact_notification, keeping it just short of 5.

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 implies the use case (look up delivery status for a notification you previously requested) and clarifies the private-vs-shared scope, but gives no explicit when-to-use guidance or pointer to request_owner_artifact_notification as the source of the request_id. Usage must be inferred.

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