bitrix24_im_message_update

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

With no annotations, description fully discloses key behaviors: wholesale replacement (no merge), author-only editing, and the risk of BBCode stripping if using wrong field. This is comprehensive for a mutation tool.

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?

Every sentence adds critical information. Well-structured: starts with purpose, then conditions, then warnings. Appropriate length for the complexity.

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 no annotations and no output schema, the description covers all essential aspects: operation, constraints, formatting, common pitfalls, and usage context. Nothing significant missing.

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?

Despite 100% schema coverage, description adds significant value for the 'text' parameter: formatting details, disclosure line requirement, and warning about using 'textRaw' over 'text'. This goes beyond schema.

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?

Description clearly states 'Edit the text of a Bitrix24 IM chat message' with specific verb and resource. Distinguishes from sibling tools like send and delete by focusing on editing existing 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?

Provides explicit constraints: only message author can edit, formatting rules (BBCode, bullet points, disclosure line), and warns against using stripped 'text' field. Gives clear instructions on constructing new text from 'textRaw'.

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