linear_getUnreadNotificationCount

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, authentication requirements, or performance characteristics. The description implies a read-only operation but fails to elaborate on important aspects like data freshness or auth scopes.

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?

The description is a single short sentence, which is efficient and easy to parse. However, it could benefit from additional critical information without becoming overly verbose.

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?

Given the complexity (one parameter, no output schema, no annotations), the description is far from complete. It does not explain the return format or the meaning of the 'limit' parameter, leaving the agent without necessary context.

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?

The schema shows a 'limit' parameter with no description, and the tool description does not explain its purpose. Without any explanation, the agent cannot determine why a limit would apply to a count operation, leading to confusion.

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?

The description 'Get count of unread notifications' clearly states the verb 'get' and the resource 'count of unread notifications', distinguishing it from siblings like linear_getNotifications (returns list) and linear_markNotificationAsRead (mutation).

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?

No guidance is provided on when to use this tool versus alternatives like linear_getNotifications or linear_markAllNotificationsAsRead. The description simply states the function without context.

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