microsoft_post_channel_message

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

The description mentions authentication routing (JWT, tenant, company scope) but fails to disclose that the tool posts a message to a channel, its effects, or any side effects.

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 short but includes redundant phrasing ('Microsoft connector operation') and routing details that could be omitted for 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?

Despite having an output schema, the description omits the core functionality (posting a message to a channel) and leaves the agent guessing what the tool actually does.

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?

With 0% schema description coverage, the description barely adds value by labeling `arguments` as a 'JSON string of arguments for the connector operation,' but provides no details on expected fields or format.

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 only restates the tool name as 'Microsoft connector operation `post_channel_message`' without clarifying that it posts a message to a Microsoft Teams channel. It does not distinguish from sibling tools like `microsoft_post_chat_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 provided on when to use this tool versus alternatives, nor any context about prerequisites or exclusions.

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