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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is partly structured. The description adds real value with '[sends a real message to a real person]', emphasizing the irreversible human-facing consequence, plus the explicit confirm:true safety gate and the read-first requirement. It does not describe failure modes or rate limits, but the impact framing is strong.

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?

Three compact sentences, front-loaded with the bracketed write/safety tag before the action. Every clause earns its place; nothing is redundant padding.

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?

With no output schema and full parameter coverage, the description supplies the key context an agent needs: it's a real write, it needs a prior read and user confirmation, and confirm:true is mandatory. Return-value behavior is unspecified, but for a write gate that is a minor omission.

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 the schema already documents chatID, text, confirm, and replyToMessageID fully. The description only echoes the confirm:true requirement already spelled out in the confirm parameter description, adding no new syntax or format detail. 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+resource: 'Send a text message to one of your Beeper conversations.' The '[WRITE]' tag immediately frames it as a mutation, and it is trivially distinguishable from the sibling read tools (beeper_list_chats, beeper_read_chats, beeper_search) and from the cross-channel telegram_send_message.

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 clear workflow prerequisites: 'You must have read the thread first and confirmed the exact text with the user. Requires confirm:true.' This tells the agent both when the tool is appropriate and what must precede it. It does not explicitly contrast with alternatives (e.g., email_send / telegram_send_message), but the channel is fixed by the tool itself, so this is a minor gap.

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