feishu_send_message

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

No annotations provided, so description carries full burden. It only states '以用户身份发送', but does not disclose authentication needs, rate limits, success/failure indications, or behavior when both text and markdown are supplied. Lacks details on whether this creates a new message vs replying.

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?

Single sentence is concise and covers purpose and supported formats. However, it omits essential behavioral details that could be included without length increase.

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 no output schema and no annotations, description is incomplete. It lacks guidance on valid parameter combinations, error handling, and authentication. For a 4-parameter tool with all optional, more context is needed for correct usage.

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 baseline is 3. Description adds no extra meaning beyond schema; it mentions support for plain text and Markdown, but schema already has separate parameters with descriptions. No clarification on mutual exclusivity of chat_id and user_id.

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 uses the specific verb '发送' (send) and resource '飞书/Lark 消息到群聊或个人', clearly indicating the action and target. It supports both plain text and Markdown, and distinguishes from sibling tools like feishu_get_messages (retrieval) and feishu_reply_message (reply).

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?

No guidance on when to use this tool vs alternatives like feishu_reply_message. Misses context for choice between chat_id and user_id or text vs markdown. No prerequisites or limitations mentioned.

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