Send Message

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

Explicitly discloses that the action is irreversible and visible to the recipient, and mentions the return value. With no annotations present, this description fully covers the important behavioral side effects.

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 brief and focused, consisting of two clear sentences with no redundant or misleading content. It is well-structured and easy to parse.

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?

While the core purpose and confirmation warning are present, the description omits details about optional parameters and does not fully compensate for the lack of an output schema. An agent would not know how to use link_preview or quoted_message_id correctly.

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%, and the description only mentions 'text' and 'idMessage'. It does not explain chat_id, message, link_preview, or quoted_message_id, leaving most parameters semantically unexplained.

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?

Clearly states the tool sends text to a chat and returns an idMessage, distinguishing it from file-sending siblings. The verb 'sends' and resource 'chat' are specific and unambiguous.

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?

Provides some usage guidance by instructing to ask for user confirmation before calling, and implies use for text messages. However, it does not explicitly mention when to prefer this tool over alternatives like send_file or send_file_by_url.

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