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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the bar is lower; the description still earns credit by making the destructiveness concrete ("reaches a real customer and cannot be unsent except by deleting it") and by stating the return payload and endpoint. No annotation contradiction; it doesn't cover error handling or whether agent_id and group_id can be combined.

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?

Front-loads "WRITE:" as the operation class, then target, delivery semantics, irreversibility and return value in three dense sentences with no filler. Every clause carries decision-relevant information.

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 destructive, non-idempotent write with no output schema, the description supplies the essentials: destination, targeting options, consequence of misuse, and return value. The one gap is what happens on failure or when both agent_id and group_id are supplied.

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%, so the schema already documents all four parameters including the random-agent semantics of group_id. The description's restatement of agent_id/group_id targeting and the clientId binding adds orientation but little meaning beyond the schema fields.

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?

Opens with an explicit verb+resource ("send an automated message") and scopes the audience precisely: a visitor bound via clientId, delivered as a pushed/automated message (POST /pushedMessages/). That 'automated/pushed' framing implicitly separates it from chatra_send_message, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

Gives a real usage constraint ("only call it with text the user asked you to send") and explains the delivery precondition (account bound to Chatra via clientId). It stops short of naming alternatives such as chatra_send_message for live replies, or saying when a pushed message is preferred over a normal one.

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