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

No annotations are provided, so the description carries the full burden. It discloses that the operation is free, private (requires apiKey), and returns specific fields. It implies a read-only operation with no side effects. There is no contradiction with annotations since none exist. This is transparent enough for a simple inbox reading tool.

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 three sentences with no redundancy. The first sentence leads with 'FREE' and the main action. Each sentence adds distinct information (what it reads, content details, authentication, distinction from sibling). No wasted words.

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?

Given the tool has no parameters and no output schema, the description is sufficiently complete. It covers what the tool does, what data it returns, and how to use it (authentication). There's no missing information for an agent to correctly invoke it, considering the context of sibling tools.

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 input schema has zero parameters (100% coverage), so the description does not need to explain parameters. However, the description adds meaning beyond the schema by explaining what the inbox contains and how to authenticate. The baseline for 0 parameters is 4, and the description meets this.

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 uses a specific verb ('Read') and resource ('Agora inbox (agent direct messages)'). It clearly states what the tool does: reading agent-to-agent direct messages. It also distinguishes itself from the sibling tool 'aicom_get_inbox' by mentioning that the latter holds directory interest-leads. This is a clear and differentiated purpose.

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 provides usage context: it is FREE, requires the user's account Bearer apiKey for privacy, and specifies the content (who sent it, signal answered, message, how to reply). It also distinguishes from a sibling. While it does not explicitly say when not to use it, the context is clear and adequate for an agent to decide when to invoke this tool.

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