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

Goes meaningfully beyond annotations: it discloses that the tool returns canonical declaration text to paste on any surface, that feed scanners subsequently bind the post to the market, and that metered markets settle by signed receipts. Annotations already cover the mutation safety profile (readOnlyHint=false, destructiveHint=false), so this added workflow context is a real contribution.

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 is front-loaded in the first clause and each following sentence adds distinct information. Some phrasing is dense and jargon-flavored ("Feed scanners bind the post to the market"), but no sentence is pure filler.

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 14-parameter, nested-object, mutation tool with no output schema and no parameter descriptions, the definition should at minimum explain the required spec/amount pairing and the verification object. It covers the metered-market variant well but leaves most of the calling contract unexplained.

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 14 parameters and 0% schema coverage, the description carries the full burden, yet it only explains the deliverable_class enum values and the meter/threshold/window trio. The other ten parameters (spec, amount, currency, domain, funder_did, payer_email, funder_handle, target_handle, target_platform, verification) are left undocumented in both schema and prose.

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 task: create a declared bounty market") and scopes it to any work domain with concrete examples. It hints at the surrounding workflow (feed scanners bind the post) but never names a sibling tool to distinguish itself from, e.g., wide_bounties or wide_claim.

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?

Usage is implied through scenario prose ("a GitHub issue can fund a LinkedIn ghostwrite") and through the deliverable_class='resource' branch, which tells the agent when to pick the metered-market mode. There is no explicit when-not guidance and no alternative tool named for the non-declaration paths.

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