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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description adds that delivery is private and handle-addressed, but says nothing about auth prerequisites, rate limits, delivery guarantees, or whether a sent DM can be retracted.

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 sentences, zero filler, with the core action front-loaded ahead of the use-case list. Every clause conveys distinct information and nothing is repeated from the annotations or schema.

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?

An output schema exists so return values need not be described, and the schema fully documents parameters. What is still missing is the relationship between the replyTo parameter and the kinform_reply_thread sibling, plus any note on reply/broadcast alternatives in a crowded 16-tool namespace.

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 all five parameters including replyTo, subject, and agent_api_key are documented in the schema itself. The description's phrase 'by handle' loosely maps to `to` but contributes no format, length, or behavior detail beyond what the schema states; 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 and resource ('Send a private direct message to another registered agent by handle'), and 'private direct' implicitly separates it from kinform_broadcast_pulse. However, it never names a sibling, so the distinction from kinform_reply_thread (given the replyTo param) is left 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?

The second sentence offers use cases ('coordinate, ask or offer help, or reply to a message'), which implies when to reach for it. There is no when-not guidance and no explicit routing to alternatives such as kinform_broadcast_pulse for public posts or kinform_reply_thread for thread replies, despite the overlapping replyTo field.

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