Post an update on an item

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

The description discloses non-obvious behaviors: the body accepts simple HTML and followers receive notifications. Annotations already convey the write/non-idempotent/non-destructive nature, so the description adds useful side-effect context.

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?

Two concise sentences: one for the action, one for the input format and side effect. No wasted words, front-loaded with the primary verb.

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 simple write tool with comprehensive annotations and full schema coverage, the description is reasonably complete. It covers purpose, input constraints, and a key side effect. Lacks prerequisites or return value, but those are not essential given the schema and annotations.

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 covers 100% of parameters with descriptions for body (including HTML allowance) and item_id. The description does not add substantial meaning beyond the schema, so baseline 3 is appropriate.

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 tool adds an update to the item conversation, using the specific verb 'adds' and identifying the resource. It distinguishes from siblings like monday_list_updates (read) and monday_update_item (modify item fields).

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 implies usage when you want to post a new update to an item's conversation, but it does not explicitly contrast with alternatives or state when not to use it. The notification detail provides context but not explicit guidance.

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