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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: a row proves recording only, not OCR accuracy or physical completion; proposals are agent-only and never charge credits, buy postage, open, forward or discard; forwarding/discard proposals are checked against the inbound policy; image URLs are never issued to agents; stop on denial rather than switching keys. This is unusually rich behavioral disclosure.

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?

Purpose and scope are front-loaded, and most sentences carry non-redundant information. It is dense and occasionally run-on (the proposals sentence is long), but there is little that could be dropped without losing behavioral or authorization detail.

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?

With an output schema present, return format need not be described. The description nevertheless covers permissions, key-scope restrictions, agent/member differences, agent-only proposal semantics, and the correct behavior on denial, so nothing an agent needs to call it safely is missing.

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 description coverage is 100%, so the schema already documents limit, offset and item_id (including paging semantics). The description only restates item_id's narrowing behavior and adds nothing on limit/offset, so the baseline 3 applies.

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?

States a specific verb and resource ('Read the inbound timeline through GET /v1/inbound-activity') and enumerates exactly what the timeline contains: received and action proposed/requested/started/completed/rejected events, newest first. It distinguishes itself from static siblings like get_inbound_item and get_inbound_mail by framing the result as an event timeline rather than item data.

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?

Gives clear context: optional item_id narrows to one item, the required scope (inbound.item.read, agent.inbox.read), and the member-vs-agent visibility rules. It does not, however, explicitly route to alternatives such as get_inbound_item_sources or get_agent_inbox_activity when a different view is wanted, so it stops short of full when/when-not guidance.

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