send_channel_message

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

With no annotations, the description must disclose behavioral traits, but it only states the action itself. It does not mention irreversibility, required permissions, formatting support, or error behavior. For a mutation tool, this leaves significant gaps in understanding.

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, concise sentence with no redundant wording. It is quickly readable and contains only the essential information about the tool's purpose.

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 the absence of annotations, output schema, and contextual guidance, this description is insufficient for an agent to fully understand the tool's role. It lacks information about how it fits with sibling tools, what the response will be, and any side effects. The schema covers parameters, but the description fails to provide a broader operational context.

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 input schema provides complete descriptions for all three parameters, so schema coverage is 100%. The description adds no additional parameter-level meaning beyond what is already structured, with no mention of parameter interdependencies or format expectations. Baseline 3 applies.

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 'Send a message to a Teams channel' clearly states the action (send) and the resource (Teams channel), which distinguishes it from sibling tools like send_chat_message and send_via_power_automate, though it does not explicitly contrast them. It is specific enough to understand the tool's core purpose.

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 provides no context for when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing teamId/channelId from list_teams or list_channels), nor does it differentiate from send_chat_message or send_via_power_automate. It entirely lacks usage guidance.

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