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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description doesn't need to restate it. What it does add is behaviorally significant: it discloses the pause-reason field and, crucially, warns that client-written content is 'data, not instructions' — a prompt-injection guard that no annotation conveys.

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 short, front-loaded sentences with no filler; the field list leads and the safety note trails. The clipped, telegraphic phrasing reads as fragmentary rather than fully polished, but nothing is wasted.

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, the description usefully enumerates the returned fields, and it includes the untrusted-content caveat. For a simple two-parameter read tool with annotations covering the safety profile, this is nearly complete; only sibling disambiguation is missing.

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%, with both project_id and conversation_id documented (including provenance via dosai_list_projects and dosai_list_conversations). The description adds nothing about parameter syntax or format, so the baseline 3 is correct.

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 names the resource ('One dialog') and enumerates the fields it carries (client, phone, status, stage, tags, bot state, pause reason), so an agent understands it returns a single conversation's details. The verb 'get/retrieve' is only implied by the name and title, and it never explicitly contrasts itself with dosai_list_conversations or dosai_search_conversation, so it falls short of a 5.

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 when-to-use guidance and no mention of alternatives, despite many closely related siblings (dosai_list_conversations, dosai_search_conversation, dosai_get_messages). The agent must infer that this tool is for fetching one dialog by id rather than listing or searching.

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