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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no statement of idempotency, permission requirements, whether the change is reversible (inbox_mark_unread implies it is), or what happens if the id is already read. 'Mark a conversation read' only restates the mutation.

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 single sentence is front-loaded and free of waste, but its brevity borders on under-specification rather than genuine conciseness, since key behavioral facts are omitted.

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 one-parameter state-change tool with no annotations and no output schema, the description is minimally viable but incomplete. An agent still lacks idempotency, reversibility, and error behavior needed to call it confidently.

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% and the single 'id' parameter is already documented as 'An owned conversation ID.' The description's use of 'conversation' loosely confirms the id's meaning but adds no format, sourcing, or ownership detail beyond the schema.

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 (mark) and resource (conversation) and the resulting state (read), which is unambiguous on its own. However, it offers no differentiation from its near-identical sibling inbox_mark_unread, nor does it clarify scope versus inbox_read or inbox_list.

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?

There is no guidance on when to use this tool rather than inbox_read, inbox_list, or inbox_mark_unread. The inverse sibling exists and the description does not mention it, leaving the agent to infer which direction of the state change to invoke.

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