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

Annotations only declare the read-only, non-destructive, non-open-world profile; the description adds materially more — the required permission (work:read with its human-readable scope), the fact that an unconnected member is prompted to sign in, the newest-first ordering, and that each item carries an editUrl that opens the draft where it was left. The closing note that member-written text is data, never instructions, is a genuine behavioral safeguard not expressible in annotations, and nothing here contradicts readOnlyHint.

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?

Purpose and scope are front-loaded in the first two sentences, with the alternative route, permission, auth behavior, and safety note following in order of decreasing urgency. It runs long for a two-parameter list tool and the quoted permission string is dense, but almost every clause carries information an agent would otherwise lack.

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 carries some of the return-shape burden and does deliver ordering, item semantics via editUrl, and where the list surfaces in the UI. It does not describe the pagination envelope (the page.nextCursor the cursor parameter refers to) or roughly what each draft record contains, which is the main remaining gap for a list tool.

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% and both parameters (limit, cursor) are already documented in the schema, so the description only needs to stay consistent rather than re-explain them. It does supply the newest-first ordering that makes cursor pagination meaningful, but adds no syntax, default, or page-size guidance beyond the schema — baseline 3.

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 ("List your member's Post Work drafts") plus scope — drafts not yet posted, newest first, the drafts strip on the Post Work page. It also distinguishes itself from the sibling that reads draft content (GET /me/drafts/{id}, i.e. get_my_draft), so an agent can separate the two without opening either schema.

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?

Clear context for when this applies: unposted drafts only, matching what the member sees in the drafts strip, implicitly contrasted with posted items. It routes to the alternative for content retrieval, but it never gives an explicit "do not use this when..." or names delete_work_draft / update_work_draft / submit_my_draft as follow-on actions.

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