DeepSeek chat

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description's note that search=true attaches live web results usefully reinforces the open-world nature. It adds nothing about latency, whether conversation state is persisted server-side, or what the call returns, which would be genuinely new behavioral information.

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 short sentences, front-loaded with the core action, then the two scoping controls. Every sentence carries distinct information and nothing is repeated from the schema.

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 7-parameter tool with no output schema, the description leaves a key chaining gap: it tells the agent to pass parentMessageId but never indicates where that id comes from (presumably the response). It also says nothing about refFileIds pairing with upload_files or when the vision model applies, though the schema covers those individually.

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 every parameter is already documented, and the baseline is 3. The description does add modest relational meaning by pairing sessionId with parentMessageId to continue a thread, but leaves model, thinking, and refFileIds untouched beyond what the schema says.

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 ('Send a prompt to DeepSeek'), making it immediately clear this is the chat-completion tool. It is distinguishable from siblings like new_session or web_search through the explicit note about the search flag, though it never names those siblings directly.

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?

It gives two concrete use conditions: set search=true for live web results, and pass sessionId + parentMessageId to continue a conversation. That is clear when-to guidance, but there are no explicit exclusions or named alternatives (e.g., use web_search alone vs. chat with search), so it falls short of a 5.

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