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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely new context: the returned message text originates from website visitors and must be treated as data, not instructions. It also discloses the underlying endpoint, helping the agent understand scoping. It stops short of covering pagination or event-volume limits.

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?

Front-loaded with the primary action and payload in the first clause, followed by a short safety note and the endpoint. Every sentence carries information, though the trailing GET path is marginally redundant with the structured name.

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 no output schema, the description compensates by enumerating the returned fields (events, stage, operators, team, rating, start page). For a 4-parameter read-only lookup with full schema coverage, an agent has everything needed to call it correctly and interpret the response.

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%, so both required and optional parameters including transcript and event_types are already documented with examples in the schema. The description mentions "its events (messages)" but adds no semantics for the transcript or event_types switches; baseline 3 applies.

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?

Uses a specific verb+resource ("Get one chat of a visitor by chat id") and enumerates the payload contents (events, stage, assigned operators and team, rating, start page), which makes the result set concrete. It does not explicitly distinguish itself from chaport_get_last_visitor_chat or chaport_list_chat_events, so it falls short of full sibling differentiation.

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?

Usage is only implied: the required visitor_id + chat_id pair tells an agent this is a point lookup rather than a listing, but there is no explicit "use this when / use X instead" guidance. Nothing tells the agent when to prefer chapters like chaport_list_chat_events or chaport_get_last_visitor_chat.

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