send_message

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'send a message to a chat,' which implies a mutating action but does not mention permissions, failure modes, or consequences. This is insufficient for an action that creates new chat content.

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, front-loaded sentence with no redundant wording. It communicates the core purpose efficiently and earns its place without unnecessary detail.

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?

For a tool with no annotations and no output schema, the description is minimal. It omits return behavior, error conditions, prerequisites, and distinctions from sibling tools. This leaves the agent with insufficient information to invoke the tool confidently in varied contexts.

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 description maps 'message' to the text parameter and 'chat' to the chat_id parameter, providing basic semantic context for both. However, it does not add significant detail beyond what the property names already imply, and with 0% schema coverage, the description only marginally compensates for the lack of parameter 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 action: sending a message to a chat, using a specific verb and resource. However, it does not explicitly differentiate from sibling tools like send_photo or send_document, nor does it specify that it is for plain text messages, so it is clear but lacks sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives such as edit_message_text or send_photo. No context is provided about prerequisites, limitations, or appropriate use cases, leaving the agent without a basis for choosing this tool over others.

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