gitee_get_notification_count

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

No annotations provided, and the description does not disclose behavioral details such as whether the parameter is required, default behavior, side effects, or return format. The read-only nature is implied but unstated.

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 with no extraneous information. It is front-loaded and efficient.

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 count tool with one optional parameter, the minimal description is adequate but lacks context about the return value (e.g., integer count) and default behavior when the parameter is omitted. No output schema is provided.

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 describes the boolean parameter 'unread' as 'Count only unread', but the tool description itself says 'Get unread notification count', creating ambiguity about whether the tool always returns unread or the parameter controls this. The description does not add clarifying context beyond the schema.

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 unread notification count' clearly states the verb (get), resource (notification count), and specificity (unread), distinguishing it from siblings like gitee_get_notification and gitee_list_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?

No explicit guidance on when to use this tool versus alternatives (e.g., gitee_get_notification for full notifications, gitee_list_notifications for lists). The agent is left to infer the use case from the name.

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