chat_update

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

No annotations provided. The description 'Update a message' gives no behavioral details: no mention of permissions needed (e.g., scopes), whether the update is irreversible, rate limits, or what the response looks like. The rich input schema hints at behavior but the description itself adds zero 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?

Extremely concise (3 words), but this is under-specification rather than efficient conciseness. The description omits critical context and should include more detail while remaining compact.

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?

With 10 parameters, no annotations, and an output schema present, the description fails to guide the agent on successful invocation. It does not explain that the tool modifies an existing message, nor does it mention the required channel and ts parameters or what the output contains.

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 baseline is 3. The description does not add extra meaning beyond what the schema already provides for parameters. No parameter reference in description.

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 'Update a message' clearly indicates the verb (update) and resource (message). While it doesn't explicitly differentiate from siblings like chat_delete or chat_post_message, the action is specific and unambiguous.

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 on when to use this tool versus alternatives (e.g., chat_delete for removing messages, chat_post_message for new ones). Does not state prerequisites like requiring an existing message.

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