Chat

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It meaningfully states that system messages become the system prompt and that output passes through a reply validator/cleaner, including a validation field for stripped content. It does not cover error behavior or side effects, but the disclosed behavior goes well beyond a minimal summary.

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?

Two dense sentences with no wasted words. The core action is front-loaded, and the behavioral details about system messages and the validation field each earn their place.

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 absence of an output schema and annotations, the description does provide useful return-relevant context via the validation field and the loaded-instance prerequisite. However, it omits guidance about generation parameters, timeout semantics, error cases, and how to obtain or reference a loaded model instance, leaving clear gaps for a tool with nested objects.

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%, so the description must compensate. It adds helpful meaning for the messages parameter (multi-message, system-role behavior), but it leaves instance_id, timeout_s, and the nested params generation settings entirely to their raw schema names and structure. This is insufficient compensation for the schema's lack of descriptions.

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 opens with a specific verb and resource: 'Send a multi-message chat to a loaded model instance.' It also explains system-message behavior, which helps identify what the tool does. It does not explicitly differentiate from chat-like siblings such as start_btw_chat, but the 'loaded model instance' scope is fairly distinctive.

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 phrase 'to a loaded model instance' implies the prerequisite of having a model loaded, giving some usage context. However, the description does not explicitly state when to prefer this tool over alternatives, when not to use it, or mention sibling tools that might be more appropriate.

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