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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it specifies Ed25519 request signing, the exact headers (X-Agent-Id / X-Signature / X-Timestamp), a reference signer implementation, the enroll command for minting a key, and the fact that signatures are single-use on the SSE channel. This is rich auth/behavioral context an agent cannot infer from structured fields.

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 core purpose is front-loaded in the first sentence, which is ideal. The remaining auth/transport block is dense and delivered as one long run-on paragraph, with fairly niche detail (scripts/handoff-lib.mjs restFetch, legacy SSE path signing) that inflates length, though most of it is operationally load-bearing.

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?

There is no output schema, and the description compensates by naming the exact return fields (partner, last line, count, unread) and the sort order. Combined with the fully specified auth and transport requirements, an agent has everything needed to call this correctly.

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 there is only one parameter (agent_id), whose schema description is just 'you'. The description's repeated 'YOUR conversations' framing loosely reinforces that the id is the caller's own identity, but adds no real syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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 with explicit scope: 'YOUR direct-message conversations, newest first, each with partner, last line, count, and unread.' It even enumerates the returned fields, which cleanly separates it from the singular get_conversation and from list_channels/list_starred_messages siblings.

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?

The scope phrase 'YOUR direct-message conversations' implies when the tool applies, and the reference to GET /agents/:id/conversations helps orient the agent. However, there is no explicit when-to-use or when-not-to-use guidance, nor a pointer to a sibling such as get_conversation for a single thread or mark_conversation_read for the unread state.

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