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

No annotations are provided, and the description steps up: it declares read-only and free (cost/safety), discloses the hard 50-item window, and states that total and unread counts are returned alongside the list. It stops short of stating the ordering guarantee or what happens when more than 50 exist, which is the only remaining behavioral gap.

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, each doing distinct work: what it returns, how to filter, and where to go instead. The differentiating content is front-loaded with no filler.

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 correctly spells out the return shape (latest 50 items plus total and unread counts), and with no annotations it supplies the safety and cost profile. Nothing an agent needs to call this correctly 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?

Schema coverage is 0%, so the description must carry the single boolean, and it does: unread_only=true returns only unread notifications, implying the unfiltered default otherwise. The default value itself is never stated outright, which is the only shortfall.

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 (list CRM notifications), names the notification types covered, and explicitly delimits itself from the sibling list_app_notifications. An agent can pick it out of a very crowded namespace without opening the 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 an explicit routing rule: app-bell notifications (billing, meetings, invitations) belong to list_app_notifications, not this tool. It also explains the one filtering option's effect (unread_only=true returns only unread), so usage and alternatives are both covered.

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