doubao_desktop_read

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

With no annotations, the description carries the full disclosure burden, and it delivers only the basic action. It does not state that this is a non-destructive read, how messages are ordered, whether pagination applies despite the limit parameter, or what happens when the conversation ID is invalid. For an unannotated tool this is a meaningful 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?

A single front-loaded sentence that wastes no words. Its brevity is efficient, though it also reflects the under-specification noted elsewhere rather than deliberate tightness.

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?

With no output schema, no annotations, and zero parameter documentation, the description should explain the return shape (message list? last N?), ordering, and the meaning of limit. None of that is present, leaving the agent under-informed for a tool it must invoke with a required ID.

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 and it largely does not. The phrase 'a specified conversation' hints at conversationId, but the numeric ID pattern (12-24 digits) is unexplained, and the limit parameter's default, maximum, and purpose (how many messages are returned) are never mentioned.

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 ('Read') and resource ('messages from a specified Doubao desktop conversation'), which cleanly separates it from write-oriented siblings like doubao_desktop_create_task. It does not, however, explicitly name or contrast itself against siblings such as doubao_desktop_sessions or doubao_desktop_status, so an agent must infer the boundary.

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?

There is no guidance on when to use this tool versus the five sibling tools, no prerequisites, and no stated preconditions (e.g., whether a task must exist or a session must be active). The agent is left to infer everything about timing and alternatives.

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