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

Annotations already cover read-only, non-destructive, closed-world, so the bar is low; the description still adds real value by disclosing the response shape (no output schema exists) and clarifying that `draft` holds not-yet-live edits in the same shape or null. It stops short of stating behavior for a missing/invalid procedureId.

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 dense sentence, front-loaded with the action and colon-introduced field list, followed by one short imperative. The enumeration is long but every item is a distinct returned field, so little could be cut without losing information an agent needs absent an output schema.

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 tool with annotations and no output schema, the description successfully substitutes for a return-value spec by naming the major fields including the conditional `draft`. Minor omissions — error/not-found behavior and the read-before-write rationale — keep it below top marks.

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?

With a single parameter at 100% schema coverage and a schema description that already tells the agent to source the id from list_procedures, the schema does the work. The description adds no format, validation, or sourcing detail beyond it, so baseline 3 applies.

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 and resource ('Read one procedure in full') and then enumerates exactly what is returned — When to use, examples, channels/inboxIds/mediums, steps, finish, subject-change behavior, status, draft. This clearly separates it from list_procedures (plural) and get_draft, though the description never names those siblings directly.

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?

The closing line 'Read it before changing it' gives a concrete workflow rule that implies when to call it, and 'one procedure' implies list-then-get. There is no explicit when-not guidance or named alternative, so usage is implied rather than spelled out.

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