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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value by explicitly stating 'Your original listing is never changed' (reinforcing the read-only guarantee on the source resource) and by enumerating the returned content (arguments, drafted header, forest status), which matters because there is no output schema.

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 opening expository clause defining 'forest' versus 'wilderness' consumes significant space without helping an agent select or invoke the tool. The description also carries embedded line breaks/indentation artifacts, and the useful scoping constraint ('Without offer_id: all your offers') is pushed to the end rather than front-loaded.

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 zero-required-param read tool with no output schema, the description does the needed work: it explains what is returned (post_listing arguments, drafted header, forest membership) and that the source listing is untouched. Auth is handled by the schema, so the remaining coverage gap is minor.

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%, so the schema already documents both offer_id and api_token, including the header-vs-parameter auth fallback. The description's 'Without offer_id: all your offers' simply restates the schema's 'Leave it out to list all your offers.' Baseline 3 is appropriate.

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 establishes that this retrieves a hashn-drafted 'forest' offer for one of the user's listings, and specifies what is shown: the post_listing arguments, the header, and its forest status. The metaphor ('forest'/'wilderness') adds cognitive load but the underlying verb+resource is recoverable. It does not directly contrast with siblings such as accept_forest_offer or post_listing.

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?

'When hashn drafts one for you, a notice names the offer; this shows it in full' implies the trigger context, and 'Without offer_id: all your offers' defines the two modes. However, no alternative tools are named and there are no explicit when-not conditions, so the agent must infer that this is a read companion to accept_forest_offer/post_listing.

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