teams_post_channel_message

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

Annotations already carry readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description usefully adds that the operation routes through a governed connector authority and that write effects require approval_ref and are verified by Spring. However, it does not clarify what side effects or destructive behavior might occur, so it only partially supplements the 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?

The description is well structured with a front-loaded operation identity and a clean Args list. Each parameter line is short and meaningful, though the opening repeats 'connector operation' and the platform path could be condensed. Overall, it earns its length without significant fluff.

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?

With seven parameters, zero schema descriptions, and the critical arguments parameter left underspecified, the description is not sufficient for correct invocation. It explains governance and approval mechanics but fails to describe the actual message-posting payload or how to discover channel/team identifiers. The output schema exists, but it cannot compensate for missing input semantics.

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 0%, so the description must compensate for all seven parameters. It gives one-line glosses for most fields (project_id, project_ref, connector_account_ref, idempotency_key, effect, approval_ref), which adds some meaning. But the central 'arguments' parameter is only described as 'JSON string of arguments for the connector operation' — a tautology that does not tell the agent what fields are needed to post a channel message (e.g., channel ID, message content).

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 name and description identify this as a Teams channel-message posting operation, but the description never states the actual effect ('posts a message to a Teams channel'). It calls it a 'connector operation' and gives the platform path, which is more label than explanation. It also does not differentiate from the highly similar sibling microsoft_post_channel_message.

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 is given for when to choose this tool over alternatives such as teams_post_chat_message or microsoft_post_channel_message. The routing statement 'Routes only through the exact project/account governed connector authority' is a constraint, not a usage condition, and does not help an agent decide whether this is the right tool for a given task.

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