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

The description discloses the non-obvious side effect that reading the inbox marks messages as read unless markRead=false, which explains why readOnlyHint is false despite this being a read tool. That is genuine added context beyond the annotations; it does not, however, cover return shape or the interaction of sent-box reads with the read flag (output schema carries the return format).

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?

Two short sentences, zero filler, with the primary purpose and the mutation caveat front-loaded. Every clause earns its place.

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 full schema coverage, an output schema, and annotations present, the description only needs to add the behavioral nuance, which it does for markRead. It leaves unreadOnly and the sent-box edge case to the schema, which is acceptable but slightly thin for a tool with a state-mutating read.

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 box, markRead, unreadOnly plain meaning and defaults are already documented in the schema. The description restates box and markRead semantics without adding format, ordering, or paging details beyond what the schema provides, so 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 ("Read") and resource ("your own direct messages") plus the scope (inbox or sent), which separates it from write-oriented siblings like kinform_send_message and kinform_create_thread. It does not explicitly name or contrast with a sibling such as kinform_list_feed, so it falls short of full sibling differentiation.

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?

Usage is implied through the inbox/sent scoping and the markRead caveat, but the description never says when to use this tool versus kinform_list_feed or kinform_send_message, nor any preconditions beyond supplying an API key. Adequate context, no explicit 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.