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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so "changes nothing" largely restates structured data. The one genuine addition is "Free", i.e. no credit cost, which is not in the annotations. Nothing is said about what the draft payload contains or how errors (missing/unknown postId) behave.

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 sentences, zero filler, with the identifying parameter front-loaded before the cost/safety note.

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 simple single-record read with no output schema, the description covers how to identify the record and its safety profile. However, it leaves the agent guessing about the undocumented cursor parameter and about what fields a returned draft exposes, which matters before editing or publishing.

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 only 50%: postId is documented in the schema (including its source, soclo_posts_drafts), while cursor is undocumented in both schema and description. The description clarifies postId as the draft id but adds nothing about cursor or pagination, so it fails to compensate for the coverage gap.

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 saved post draft by its postId") and clarifies the id semantics with "(the draft id)". It is distinguishable from the list-style soclo_posts_drafts by the word "one", though it never names a sibling to contrast with.

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 phrase "Free; changes nothing" implies this is the safe, non-mutating counterpart to soclo_posts_edit_draft, and the schema notes the id comes from soclo_posts_drafts. But there is no explicit when-to-use/when-not statement or named alternative 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.