list_notifications

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

No annotations provided so description bears full burden. It discloses auth requirement, ordering, and that both read/unread are included. However, it does not explicitly state that it is read-only or describe any side effects, pagination, or rate limits.

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?

Single sentence that front-loads the key information. Every word earns its place; no wasted text.

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 simple list tool with no parameters and no output schema, the description covers the essential: resource, ordering, auth. Could mention output fields but not critical given straightforward nature.

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?

No parameters (0), so schema coverage is 100% vacuously. Baseline is 4. Description adds no parameter info but none is needed.

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?

Clearly states verb (list), resource (price alert notifications), scope (authenticated user), and ordering (newest first). Distinguishes from sibling tools like get_unread_notification_count and mark_notification_read by specifying it returns both read and unread notifications.

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?

Implied usage to list all price alert notifications, but does not explicitly state when to use this tool vs. alternatives (e.g., get_unread_notification_count for just the count). No when-not guidance provided.

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