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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so "changes nothing" is largely redundant. The description does add two things not in the annotations: the cost ("Free") and the paging model ("cursor paging"). It still omits result ordering and what a draft record contains, but given the annotation coverage this is solid added context.

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, no filler, and the core action is front-loaded before the cost/side-effect note. Efficient for a one-optional-param read tool, though the terseness leaves obvious semantic gaps unaddressed.

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?

No output schema and only one optional parameter keep the structural burden low, and annotations cover the safety profile. Still, in a namespace crowded with draft-related tools (posts_get_draft, posts_list, posts_save_drafts, posts_edit_draft, autopilot_drafts, work_drafts_read), a complete definition would clarify scope and which drafts are returned.

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?

The single `cursor` parameter has 0% schema description coverage, so the description must carry it. "with cursor paging" correctly frames cursor as a pagination token, but doesn't say where the cursor comes from (a prior response) or that omitting it returns the first page. That is partial compensation 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?

"Read ... saved post drafts" gives a specific verb and resource, and "with cursor paging" signals list semantics rather than fetching a single draft. The qualifier "actual saved" distinguishes it from cached/mirror views. However, it does not name the nearest siblings (soclo_posts_get_draft, soclo_posts_list, soclo_autopilot_drafts) that an agent must choose between.

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?

"Free; changes nothing" tells the agent the call is cheap and side-effect-free, which implicitly encourages using it to inspect drafts. But there is no explicit when-to-use/when-not, no statement of how it differs from soclo_posts_get_draft or soclo_posts_list, and no prerequisites (e.g., account/page context).

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