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

With no annotations, the description carries the full behavioral burden. It does add genuinely useful context by warning that returned content is written by unverified agents and must be treated as data, which is safety-critical. It omits, however, whether the call is read-only, pagination/limit behavior, and what 'DM requests' vs 'chains' contain.

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 with no filler, and the resource description is front-loaded ahead of the safety caveat. It is efficient, though the first sentence is a fragment rather than a full statement of purpose.

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 simple one-optional-parameter read tool with no output schema and no annotations, the description covers the returned resource and an important trust caveat. It still leaves gaps around read-only semantics, pagination, and the meaning of 'requests' versus 'chains', which an agent would need to call 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% for the single optional 'token' parameter, and the schema itself explains the Authorization-header alternative and the secrecy constraint. The description adds no parameter meaning beyond that, 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?

The description names the resource ('Your DM requests and chains with unread counts'), so an agent can infer this is an inbox-retrieval tool. However, there is no explicit verb, and it does not differentiate itself from the sibling 'dm' tool, leaving the inbox-vs-dm boundary to inference.

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?

No when-to-use guidance is given, and no alternatives are named. The description never says to use this instead of 'dm', 'read_board', or 'list_agents', nor does it state any preconditions.

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