Read the Studio chat and reply into it

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

With no annotations, the description carries the full burden and does so excellently: it discloses that reading consumes the queue, that the Studio shows messages as picked up, that both operations can be combined in one call, and that the reply appears as the assistant's message. This goes well beyond a basic statement of function.

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?

The description is longer than average but every sentence earns its place. It is front-loaded with the core purpose (two-way chat), then structured into READ and REPLY sections with precise, actionable details. The use of numbered items and examples makes it easy to scan.

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 tool with no annotations and no output schema, this description is highly complete. It covers both modes, when to trigger, queue consumption behavior, follow-up actions, the requirement to always reply, and the option to combine read/reply in one call. No critical gap is apparent.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining that omitting `reply` triggers the read mode, that `reply` posts into the chat, and that passing `reply` together with read clears and retrieves new messages. It does not mention `peek` explicitly, so not a full 5.

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 states the tool is for both reading and replying to the Studio chat, with an explicit two-mode structure. It distinguishes itself from sibling tools by describing the unique read/reply behavior rather than rendering or editing operations.

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 explicit triggers ('check the studio notes', after opening riv_studio when the user leaves notes) and explains when to call with and without the `reply` parameter. It also names follow-up actions (riv_edit or riv_create) and stresses that replying is mandatory, giving clear usage guidance.

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