chatter_post

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

The description adds behavioral details beyond annotations: default needs an approval token from a preview call, and a direct mode bypass. This is useful additional context, though it does not fully disclose all side effects like notifications or record creation.

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 very concise, using only two sentences. The first sentence states the core purpose, and the second adds important usage variation. No unnecessary words.

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 (destructive, 9 params, approval requirement), the description is somewhat incomplete. It does not explain how to obtain the approval token (likely from the preview_write sibling), nor does it describe error conditions or the output schema content.

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 partially explains the 'approval' parameter as a token, and implies the direct mode via environment variable. However, it does not describe other parameters like partner_ids, attachment_ids, or message_type, which remain undocumented.

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 clearly states the action ('Post') and the resource ('chatter message on a mail.thread record'). It is distinct from sibling tools, none of which seem to post chatter messages.

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 explains two usage modes (default requiring approval token, direct bypass with env variable). It gives context on when to use the direct mode, but does not explicitly contrast with alternative tools or state when not to use it.

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