send_message

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

No annotations are provided, so the description carries the full burden. It specifies that only plain text is sent but does not disclose authentication requirements, idempotency, error handling, or what happens if the room_id is invalid. This is insufficient for a mutation tool.

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 a single sentence, front-loaded, and concise. It efficiently communicates the core action without unnecessary words, though it could include more detail without harming brevity.

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 that the tool has only two simple string parameters and no output schema, the description provides adequate context for the basic operation. However, it lacks any guidance on success/error responses or retries, which marginal completeness for a simple tool.

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 0%, meaning no parameter descriptions in the schema. The description only gives context for 'room_id' (private chat, group, channel) but does not elaborate on 'msg' beyond 'plain text', nor any format constraints like minimum length is already in schema. It fails to compensate for the lack of schema descriptions.

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 clearly states the verb 'send', the resource 'plain text message', and specifies the target destinations 'private chat, group, or channel room'. This distinguishes it from sibling tools like 'comment_channel_post' (which comments on a post) and 'list_messages' (which retrieves messages).

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?

The description implies the tool is for sending plain text only, but it does not explicitly state when to use it versus alternatives like 'comment_channel_post' or when not to use it (e.g., for messages with attachments). No prerequisites or constraints are mentioned.

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