teams_post_chat_message

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

Without annotations, the description carries the full burden of disclosing behavioral traits. It only mentions routing and authentication scope but does not indicate whether the operation is destructive or read-only, rate limits, or side effects. Minimal transparency.

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 brief (two sentences) and front-loaded with the purpose. However, it includes routing details that may not be necessary for the agent. It is concise but could be more informative.

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 tool's complexity as a generic wrapper, the description is incomplete. It does not explain how to construct the arguments JSON, describe the output (even though an output schema exists), or mention constraints. The agent would lack sufficient context to use the tool effectively.

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 says 'arguments: JSON string of arguments for the connector operation', which adds no meaning beyond the input schema (which has a string parameter with no description). With 0% schema coverage, the description fails to compensate by explaining what keys the JSON should contain.

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 states it is a 'Teams connector operation `post_chat_message`', which indicates posting a chat message in Teams. However, it does not specify the destination (chat, channel, or user) or distinguish itself from similar sibling tools like `microsoft_post_chat_message`. The purpose is clear but lacks specificity.

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. There are sibling tools like `teams_post_channel_message` and `microsoft_post_chat_message`, but no criteria for selection are mentioned.

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