agent_inbox

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the filtering scope (unacknowledged messages sent to this machine by other agents), but it is truncated mid-sentence and does not explain whether reading marks messages as acknowledged, what permissions are required, or what the response contains.

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 that cuts off mid-parenthetical ('it needs...'), leaving it structurally incomplete. While the opening is front-loaded and efficient, the truncation undermines its usefulness.

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 tool with no output schema and no annotations, the description should at least explain the return format or the expected workflow (e.g., acknowledge after reading). The truncated sentence leaves a significant gap in completeness.

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?

With zero parameters, there is no parameter semantics burden. The schema coverage is reported as 100%, and the description correctly does not introduce unnecessary parameter details.

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 states a specific verb ('Reads') and resource ('messages other agents sent to this machine') and scopes it to messages not yet acknowledged by this agent_id. This distinguishes it from sibling tools like agent_ack and agent_send, though the sentence trails off before naming alternatives explicitly.

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 by saying messages are 'not acknowledged yet,' but it does not explicitly state when to use this tool versus agent_ack or agent_send, nor does it mention follow-up actions such as acknowledging messages after reading.

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