chat_read

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

Describes that attachments are returned as a list with name, size, disk_id, and notes that download links are excluded. With no annotations, this adds useful behavioral detail. Could mention response structure more but output schema exists.

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 sentences, front-loaded with purpose, no wasted words. Efficient and clear.

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?

Covers basic purpose and attachment info, but doesn't explain overall return format (messages) or usage context for boolean parameters. Output schema exists but description still leaves gaps.

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?

Only 40% of parameters have schema descriptions. The description adds no extra meaning for 'full', 'limit', or 'include_system', which remain undocumented. It reiterates chat_id/user_id purpose already in 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?

Clearly states it reads a dialog where the user is a participant, distinguishing it from sibling tools which are unrelated. Verb 'read' with specific resource 'dialog', and specifies both group chat and personal chat.

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?

Implicitly restricts to dialogs where the user is a participant, but does not explicitly mention when not to use or provide alternatives. Clear context for when to use.

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