get_unread

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

With no annotations, the description discloses that messages are marked as read after retrieval, behavior depends on background service, and response includes has_more for pagination. Missing details on authentication or rate limits but adequate.

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?

Front-loaded with purpose, then conditional behavior and key traits, all in a few concise sentences. No extraneous information.

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 single-param tool with no output schema, the description mentions the key behavior and pagination flag. Could describe the message object structure, but overall it's sufficient.

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?

Schema coverage is 100% for the only parameter 'limit'. Description adds a pagination hint ('call again with a higher limit or paginate') but the schema already defines its meaning. Minimal added value.

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 'Get new unread messages' and indicates it is the tool to use for checking new messages, distinguishing from siblings like 'receive_messages' or 'search_messages'.

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?

It explicitly says 'Always use this to check for new messages' and explains conditional behavior (service vs polling) and pagination hint. However, it does not explicitly exclude use cases like retrieving without marking as read.

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