Send message to phone

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

Annotations already declare destructiveHint=true, and the description adds valuable context about temporary contact lifecycle ('may create a temporary contact', 'contact_was_new / contact_removed') and the rich mode restriction. This goes beyond the annotation without contradicting it.

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 two sentences plus a documentation link. It front-loads the primary purpose, includes the most important caveat, and mentions success output fields in a compact way. No fluff or repetition.

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?

Given the tool's complexity (8 parameters, output schema, annotations), the description covers the core purpose, temporary contact behavior, rich mode limitation, and result fields. It doesn't explain prerequisites like 'phone must be on Telegram', but that is in the schema. A documentation link further fills gaps. Sufficiently complete.

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?

The schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The description's note that 'parse_mode=rich cannot be combined with files' is helpful but is also present in the schema's parse_mode description. No additional parameter semantics provided beyond schema.

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 opens with 'Send to a phone number', clearly stating the action and specific resource. It also mentions the temporary contact creation and text/file sending, which distinguishes it from sibling tools like send_message that likely operate on existing chats.

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 clearly implies the use case (when you have a phone number) by starting with 'Send to a phone number'. It does not explicitly mention alternatives or exclusions, but the phone-number focus is clear enough to guide tool selection. Lacks an explicit 'use send_message instead when you have a chat ID' style note, so not a 5.

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