Share text or a link into the meeting

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

With no annotations, the description carries the full burden. It discloses the important behavioral fact that the message is posted under the bot's identity and lands in the same channel as send_chat, but says nothing about delivery guarantees, permission/prerequisite requirements (bot must be in the meeting), length limits, or failure modes.

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?

Three short sentences, front-loaded with the core action, and the parenthetical exclusion is compact. Minor waste in the parenthetical phrasing ('say does that') but nothing is padded.

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 two-parameter tool with a fully documented schema and no output schema, the description covers action, identity, and channel. The remaining gap is the unresolved relationship with send_chat, which an agent would want resolved before picking between the two.

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 100%, so both parameters are already documented including the 2000-character limit and where meeting_id comes from. The description adds no syntax or format detail beyond what the schema provides, so 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?

States a specific verb and resource: posts text into the meeting chat as the bot, and pins down the channel identity by tying it to send_chat. It does not, however, explain how it differs from send_chat despite claiming the same channel, which leaves the closest sibling ambiguous. The title also promises link sharing that the description never addresses.

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?

It gives negative routing ('does not speak — say does that', 'does not share a screen'), which is genuinely useful for excluding siblings. But it never states when to choose this over send_chat, the one tool it explicitly says shares the same channel, so the key selection decision is left to inference.

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