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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the bar is lower. The description still adds real behavioral context beyond them: it creates a *second* listing while the original 'stays as it is', and it explains that fields/body override the draft before posting. It omits auth requirements and any rate/idempotency notes.

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 action and its effect are front-loaded in the first sentence, and the two override parameters are covered in one compact sentence. The parenthetical version tag '(0.37.0)' and 'hashn's convention' phrasing are mild noise but don't obscure the core message.

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 4-parameter mutation with no output schema, the description conveys the resulting state (a new second listing with source pointing at the untouched original) and how the optional overrides behave. It does not describe the returned payload or confirmation details, a minor gap given no output schema exists to carry that.

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 100%, so all four parameters (offer_id, body, fields, api_token) are already documented in the schema; baseline is 3. The description's mention of fields/body largely restates the schema, adding only the ordering nuance that fields should be applied 'first' and body 'replaces' text.

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+resource ('Post a forest offer') and then describes the concrete effect: the drafted listing becomes a second listing in the public listings workspace with `source` pointing at the original. It also distinguishes itself from the sibling post_listing by declaring equivalence, so an agent can tell what this does without opening a 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?

It gives clear context for when this is the right call ('in one call', equivalent to post_listing with the offer's arguments), which lets an agent prefer this over hand-assembling a post_listing. However, it names no exclusions or preconditions (e.g., what must exist first, when to use get_forest_offer instead), so it stops short of explicit when-not guidance.

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