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

Annotations already establish readOnly/openWorld=false/destructive=false, but the description adds real value: it discloses that the tool reports whether the last run is still running or why it found nothing, that counts are windowed to 30 days, and that posting is explicitly out of scope. Pagination and output format are unstated, keeping it from a 5.

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?

The content is front-loaded and the colon-delimited enumeration is readable, but the whole definition is one sprawling sentence with an orphaned 'Free.' trailing at the end, which adds little and weakens structure.

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-only tool with no output schema, the description carries the return-value burden well by enumerating the fields an agent will see. The missing piece is any indication of volume/pagination or ordering, but overall it is close to sufficient.

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 0% for the single platform parameter, so the description must compensate. It implies scoping via 'for one platform,' which maps to the parameter, but never states the reddit/x values or what 'Assisted' means operationally — only partial compensation.

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?

The description states a specific resource (drafts on Assisted posts) and scope (one platform), and enumerates what it returns: run status, counts left/posted in 30 days, each draft's thread/post, and page link. It doesn't name or differentiate against its likely siblings reach_find or reach_mark, so it stops short of 5.

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?

It gives an explicit behavioral constraint — 'The founder posts from that page; never post or paste a draft yourself' — which tells the agent what not to do with the drafts. However it never says when to call this versus reach_find/reach_mark, so usage guidance is only partly covered.

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