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

No annotations are provided, so the description carries the full burden. "Proof-gated" is the only behavioral hint, and it is never explained — what proof is required, how it is supplied, or what happens on failure is all unstated. This is a significant gap for a mutation-style tool with zero annotation coverage.

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?

A single short phrase, front-loaded with the core action. It is efficiently sized, though the terseness edges toward under-specification rather than economy.

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?

With no annotations, no output schema, and an unexplained "proof-gated" constraint, the definition leaves the agent without the operational detail it needs to call this tool correctly. Zero-parameter tools still need the gating condition spelled out.

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?

The tool takes zero parameters, so the schema description coverage baseline of 4 applies. There is nothing for the description to add or compensate for here.

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 verb+resource ("post an in-kind offer"), which is enough to distinguish it from the sibling post_need by domain. However, "in-kind" is unexplained jargon and "proof-gated" is left opaque, so the agent knows roughly what it does but not the substance of the action.

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?

No when-to-use guidance, no prerequisites, and no explicit routing versus siblings like post_need or ledger_check. The agent must infer usage purely from the name.

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