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, so safety is covered; the description adds the return-shape contract (a single integer) that annotations cannot express. It would earn a 5 with a note on freshness/caching (is the count live or eventually consistent) or on scope (account-wide vs course-scoped), which matters for an openWorld read.

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?

One front-loaded sentence carries the purpose plus both disambiguations via em-dash appositives, and a second sentence carries the routing. No filler, no restatement of the title.

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 with annotations covering the safety profile and no output schema, the description supplies what the structured fields cannot: the exact return type and the semantic boundary of the count. Nothing an agent needs before calling 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?

The schema has zero parameters, so there is nothing for the description to disambiguate — baseline 4 applies. The description correctly implies no filtering inputs exist by scoping the result to 'the authenticated user' rather than inviting user/workspace arguments.

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 ('get the number of unread conversations for the authenticated user') and immediately disambiguates the two plausible misreadings: not the conversation objects, and not a count of unread messages inside them. That double negation makes it trivially separable from list_conversations and get_conversation.

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?

Explicitly routes the agent elsewhere when this tool is the wrong choice: list_conversations to enumerate which conversations are unread, get_conversation to open one. It even notes that opening a conversation marks its messages read, which is the side effect an agent must consider before calling that sibling.

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