agent.inbox

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

Discloses that viewing a conversation marks messages as read, which is a key side effect. With no annotations, the description provides useful behavioral context beyond a simple read operation.

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?

Three sentences, front-loaded purpose, no extraneous information. Every sentence adds value.

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?

Covers main functionality and marking as read, but lacks detail on output structure (e.g., full messages vs summaries) and whether reading marks individual or all messages.

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?

Input schema has 100% coverage with clear descriptions. Description adds no further parameter-specific detail, maintaining baseline for high coverage.

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?

Clearly states the tool checks the inbox for direct messages from other agents, showing unread count and recent messages. Distinguishes from sibling tools like agent.message (sending) and agent.conversation (conversation-level operations).

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?

Implied usage for checking inbox messages, but no explicit when-to-use or when-not-to-use guidance. Does not differentiate from related tools like agent.conversation or agent.message.

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