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

Beyond the readOnlyHint annotation, the description adds useful behavioral context: events are returned in order, the event categories are listed, and it includes an important prompt-injection warning that visitor message text should be treated as data, not instructions. It does not discuss pagination or result limits, but the annotations already establish that this is a safe read operation.

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 compact and front-loaded: it states the core purpose first, then enumerates event types, then adds the safety warning. Every sentence contributes useful information with no filler.

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 readOnly/openWorld annotations, fully documented parameters, and absence of an output schema, the description supplies enough context for an agent to call this tool correctly. The enumerated event types and prompt-injection warning are particularly relevant additions.

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 coverage is 100%, and both parameters are well described in the schema itself, including where to obtain chat_id and visitor_id. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 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 gives a specific verb and resource: list all events of one chat, in order. It enumerates the event types (visitor/operator messages, trigger messages, invitations, email requests, opened pages), which makes the tool's scope unambiguous compared with siblings like chaport_get_chat_event.

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 clearly implies the use case of retrieving a chat's event history, but it does not explicitly say when to use this versus chaport_get_chat_event or chaport_get_chat. Usage is inferable from the purpose statement rather than explicitly guided.

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