dat_chat

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

Describes key behaviors (NDJSON streaming, built-in tools, tool-streaming incompatibility) but with no annotations, misses return format and error details.

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?

Three concise, front-loaded sentences, each adding essential detail with no redundancy.

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?

Adequate for a chat tool but lacks output schema description and doesn't cover error cases like enabling tools with streaming, leaving some gaps for agent understanding.

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 covers all parameters with 100% description coverage; description adds value for streaming/tools interplay but doesn't enrich individual parameter meanings beyond schema.

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 clearly identifies the tool as an Ollama-compatible chat endpoint via dat.ai, distinguishes it from sibling browsing/transcription tools by its chat function.

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?

Provides clear usage context: streaming vs non-streaming, and the constraint that tools cannot be used with streaming. However, lacks explicit differentiation from sibling dat_completions.

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