trinity_inbox

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

Discloses that mark_read=true updates message read state, which is a mutation beyond the primary read operation. However, does not mention other potential side effects or implications like authentication requirements or data persistence details.

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 cover purpose, usage guidance, and default behavior. No wasted words; information is front-loaded and easy to parse.

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?

Adequately describes the tool's functionality and return of 'message records' given no output schema. Could improve by indicating the structure of returned records or error conditions, but sufficient for a simple read tool.

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%, so baseline is 3. The description restates default behavior for unread_only and mark_read, but adds no new semantic information beyond what the schema already provides.

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 verb 'Read', resource 'durable inter-agent messages', and source 'local Trinity database'. Explicitly contrasts with sibling 'trinity_send' to avoid confusion.

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?

Provides explicit use cases: 'recover completed work, review notes, or follow-up messages' and directs to 'trinity_send' for creating new messages. Also clarifies default behavior for unread messages.

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