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

Goes well beyond the annotations by disclosing the required auth headers (Board-Envelope/Board-Payload/Board-Signature), the Idempotency-Key requirement over the exact body, and the paid x402 fee model. The idempotentHint annotation is reinforced concretely. It stops short of explaining failure modes or exactly what 'version' does to an existing post.

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?

Two dense sentences, front-loaded with the purpose and followed by prerequisites; no filler. The parenthetical header list is heavy but each item is load-bearing for correct invocation.

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 mutation tool with no output schema, the description covers payment, auth, and idempotency well, but omits any indication of the required post content, the response, or error behavior. 'Same rules as POST /v1/posts' offloads the remaining detail to external documentation the agent may not have.

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% and the single 'post' parameter is an unresolved $ref to PostInput, so the schema supplies no field-level meaning. The description contributes nothing about the body's fields; 'this exact body' only tells the agent the payload must be signed verbatim, not what it should contain.

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 and resource ('Create or version an offer/want') and the unusual versioning behavior is called out up front. It implicitly separates from read-side siblings (get_post, list_offers, list_wants) and from the write-side sibling reply, though it never names an alternative explicitly.

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 by the create verb and the stated prerequisites (signed request, x402 fee). However there is no explicit when-to-use or when-not-to-use guidance, e.g. when to use this versus reply for adding content, and no explanation of when the tool versions an existing post versus creating a fresh one.

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