get_conversation_unread_count

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

The description adds the context 'for the authenticated user,' which is not in annotations. However, annotations already include readOnlyHint: true, and the description does not disclose further behavioral traits (e.g., return format or rate limits). It does not contradict 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?

The description is a single sentence with 13 words, front-loading the key action and resource. Every word is necessary, and there is no verbosity.

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 parameterless tool with no output schema, the description adequately conveys what the tool does. It is complete enough for an agent to understand its purpose without missing critical information.

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 provides full coverage. The description does not need to add parameter semantics; baseline is 4 for 0 parameters.

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 clearly states the verb 'Get', the resource 'number of unread conversations', and the scope 'for the authenticated user'. It is specific and distinguishes from sibling tools like get_conversation or list_conversations, which deal with conversation details or lists.

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 description implies usage for retrieving the unread count for the authenticated user, but does not explicitly state when to use it versus alternatives or provide exclusion criteria. Nonetheless, the context is clear enough for an agent.

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