Get Conversation Unread Count

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and volatility. The description adds no new behavioral context beyond the read-only count scope; it does not explain response shape, auth-specific edge cases, or what 'unread' means, but it also does not contradict the annotations.

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?

A single sentence with no redundant wording. The action and target are front-loaded, making it immediately scannable.

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 zero-parameter, read-only count operation, the description is sufficiently complete: it states what is returned (a count), for whom, and of what resource. No output schema exists, but 'the number of unread conversations' makes the return intent clear enough.

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?

There are zero parameters, so the schema has nothing to document and the baseline for this dimension is 4. The phrase 'for the authenticated user' communicates the implicit auth context relevant to the tool's operation, but no parameter meaning 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?

The description uses a specific verb ('Get') and a precise resource ('the number of unread conversations'), and scopes it to the authenticated user. It is clearly distinguishable from siblings like list_conversations or get_conversation by its aggregate-count intent, though it does not explicitly name those alternatives.

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?

The use case is implied: call this when you need the unread-conversation count for the current user. However, there is no explicit when-to-use/when-not-to-use guidance or any mention of alternatives such as list_conversations, so an agent must infer the decision on its own.

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