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

Annotations only declare readOnlyHint and openWorldHint; the description adds real value beyond that by enumerating what the response contains (stage values, assigned operators/team, rating, missed flag) and by disclosing the GET endpoint. It also carries an important prompt-injection warning about visitor-authored message text. It does not say how many events are returned or whether the list is truncated, which is the remaining behavioral gap.

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 core purpose, then dense clauses that each carry information (stage values, links.more behavior, injection warning, endpoint). It is a long single block of clauses rather than clearly separated sentences, which slightly hurts scanability but wastes no words.

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?

No output schema exists, so the description must carry the return-value burden, and it does so thoroughly by naming the fields an agent would act on. The only omissions are transcript-mode behavior and any indication of event limits or pagination.

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 transcript and event_types are already well documented in the schema, which sets the baseline at 3. The description adds little parameter-level detail and never mentions the transcript mode that materially changes the return shape, so it does not exceed the baseline.

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?

Specific verb and resource: 'Get a visitor's current or most recent chat' with an explicit enumerated payload (events, stage, operators, rating, start page, missed). It also names the sibling boundary by pointing at chaport_get_chat for older chats, so an agent can distinguish it from chaport_get_chat and chaport_list_chat_events without opening a schema.

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?

Implies the selection rule (latest chat for a visitor) and explicitly routes to chaport_get_chat for older chats via links.more numeric ids. There is no explicit when-not or a comparison against chaport_get_chat_event or chaport_list_chat_events, so it stops short of full routing guidance.

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