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

Beyond the annotations' idempotent/non-destructive hints, the description discloses important mutation semantics: for one-to-one chats only incoming direct-message notices are affected, while shared project notices are unchanged; for group chats the read position advances to the newest message and never moves backward. This is substantive behavioral context an agent could not infer from annotations alone.

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 description is three tightly written sentences with the core action and scope front-loaded. Every sentence adds distinct value: what is affected, how to obtain parameters, and which sibling to use for reading.

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 two-parameter mutation tool with annotations covering idempotency and destructiveness and no output schema, the description covers the necessary ground: action, scope, parameter sourcing, read-position behavior, and the read-vs-mark-read distinction. Nothing essential for correct invocation 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 0%, so the description must compensate. It does so by explaining that chat_id and item_ids should be sourced from read_chat or list_unread_chats, adding provenance and linkage beyond the raw UUID schema. It does not elaborate on constraints such as item_ids belonging to the same chat or the 200-item limit, so it is not fully compensatory.

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 action — marking AccountHub chat messages as read — despite the potentially confusing tool name 'read_direct_chat'. It explicitly distinguishes one-to-one direct-message notices from group/shared-project notices and names the sibling 'read_chat' as the tool for actually reading messages.

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?

It tells the agent exactly when to use this tool versus the alternative: 'To read messages use read_chat; this only marks them read.' It also specifies where the required parameters come from ('read_chat / list_unread_chats'), removing ambiguity about invocation context.

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