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

Annotations establish this is a mutation (readOnlyHint=false) that is non-destructive and closed-world. The description adds real behavioral context beyond that: the draft leaves the waiting queue, is never offered again, and a posted draft with a reply link is recorded as shipped (Claimed). These consequences are not inferable from the annotations alone.

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?

Front-loads the trigger condition and effect in dense, purposeful sentences with no filler. The trailing 'Free.' is terse and adds a useful cost signal, though the run-on first sentence is slightly crowded.

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 exists, and the description covers the invocation trigger, side effects, and id provenance, which is nearly everything an agent needs for a non-destructive 4-param mutation. Only the platform parameter's meaning is left entirely to the schema.

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 50% schema description coverage, the description usefully clarifies url semantics ('the link of their reply, when posted') and implicitly the status values. However, the platform enum is never explained and status enum values carry no prose, so it only partially compensates 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 (mark) and resource (draft posted/skipped) and describes the effect: 'leaves the drafts waiting and is never offered again' and 'recorded as shipped (Claimed)'. It references reach_drafts as the id source but doesn't explicitly contrast against siblings like reach_drafts or shipped, so it's clear but not fully self-differentiating.

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?

Gives a concrete trigger: 'When the founder says they posted a draft (or will not), mark it'. This is a clear condition for invocation and points to reach_drafts as the origin of ids. It stops short of naming an outright alternative to use instead, so 4 rather than 5.

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