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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's value-add is its disclosure of return content. With no output schema, it explains the status enum values, distinguishes step kinds ("call" carries a tool, "say" does not), and notes a step may also carry say content. That is real behavioral context beyond the annotations.

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 opens with the verb and resource, then layers the return detail. It is dense and uses nested parentheticals, but each clause documents a distinct return field that has nowhere else to live without an output schema, so the length is largely justified.

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 one-parameter, read-only tool with no output schema, the description covers the important return surface: status values, reply, step structure, proposal, estimate, question, plan, and changes. Safety is handled by annotations. A brief note on error/not-found behavior would close the remaining gap.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents turn_id and its origin. The description adds no syntax, format, or constraint detail for turn_id. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb+resource ("Read a turn") and enumerates exactly what a turn yields: status, reply, steps, proposal, estimate, question, plan, changes. The resource (turn) is clearly distinct from siblings like get_chat, get_run, and get_project. It lacks explicit sibling differentiation, but the purpose is unmistakable.

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, no mention of alternatives such as get_run or get_chat, and no stated prerequisites. The only usage clue is indirect, via the turn_id schema description ("from send_message"), which implies sequencing but is not in the description itself.

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