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

Goes well beyond the annotations by disclosing that auth is required, that it is free with credit or x402 payment options, the one-review-per-item limit, and where the content surfaces (item page and Requests board, marked verified buyer). A write tool with readOnlyHint=false is well covered here, though the payment phrasing is terse.

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?

Four dense sentences that are front-loaded with the core action and each carry distinct information (scope, auth/cost, limits, visibility, content advice). Slightly telegraphic parentheticals like 'with credits, or over x402 from its payout wallet' reduce readability marginally.

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 no-output-schema write tool with two alternative target parameters, the description supplies auth, cost, rate limit, and post-visibility context, which is most of what an agent needs. It omits confirmation/return behavior and the review-vs-report distinction, keeping it short of fully complete.

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 only 25% schema coverage, the description carries the load by clarifying that the target is 'a unit or a dataset' (mapping to unitId vs dataset) and that the content is a 'review or a question' (mapping to the kind enum). It does not explain body length limits, but it meaningfully compensates for the low coverage.

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 review of, or a question about, a unit or dataset the operator bought. This clearly separates it from acquisition siblings like buy_dataset and read/query tools, though it never names a sibling directly. The dual review/question nature is spelled out up front.

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?

Provides a scope rule ('one review per item; questions as needed') and content guidance ('be specific: what held, what did not'), which implies usage. However it never clarifies when to use this versus adjacent tools such as report_content or post_request, so the agent must infer the boundaries.

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