read_chat

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

With no annotations, the description carries the full burden, and it does disclose the shape of the result (what was asked plus each turn's final answer). However, it says nothing about read-only safety, permissions, pagination, or what happens when the chat is not found, leaving meaningful behavioral gaps.

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?

A single front-loaded sentence with no filler, and the parenthetical qualification of the chat identifier is placed immediately after the object it describes. Every clause carries information.

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?

For a four-parameter, unannotated tool with no output schema, the description covers the retrieval concept but omits the semantics of three parameters and any limits on how many messages are returned. Adequate to call the tool in the simplest case, but incomplete overall.

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 0% across four parameters. The description clarifies only one of them (chat accepts an id or exact title), which is useful, but app, last, and project are left entirely undefined with no format, meaning, or default explanation.

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 states a specific verb and resource ("Read the last messages of a chat") and scopes the result to questions and per-turn final answers, which clearly separates it from siblings like send_message or list_chats. It does not explicitly name an alternative, so it stops short of a 5.

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 verb and scope imply the use case (fetching recent conversation content), but there is no explicit when-to-use or when-not-to-use guidance, and no mention of how it relates to siblings such as list_chats or wait_reply. Usage is inferable rather than stated.

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