⚠️ Отправить сообщение

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

Description confirms the destructive nature (sends real message) and adds context that it is visible to the buyer, which is beyond the annotations' destructiveHint: true. No contradiction with annotations.

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 short sentences, front-loaded with a warning icon and key information. No wasted words, efficient and direct.

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?

Despite good annotations and schema, the description lacks information about the return value (no output schema) and does not cover behavior of dryRun or idempotencyKey parameters, which are documented only in schema. For a sending tool, the response is important context missing.

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%, and the description mentions the text length limit (already in schema). No additional semantic value added beyond what the schema provides for parameters.

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?

Description clearly states it sends a real message to the client in chat, specifying it is for text (up to 1000 chars). The sibling tool for image messages (messenger_post_send_image_message) is distinct, so purpose is well-defined and differentiated.

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?

Explicitly warns to confirm with user before calling because the message is visible to the buyer. This provides important usage context. However, it does not explicitly mention when to use this tool over alternatives (like image messages), which is partially implied by the name and description.

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