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

Annotations only mark it non-read-only/non-idempotent/non-destructive; the description goes well beyond that with on-chain mirror-node verification, anti-fabrication guarantee, one-review-per-transaction enforcement, no-self-review rule, content filtering, max length, rating bounds, and a per-agent daily rate-limit quota. This is exactly the extra behavioral context that annotations cannot carry.

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?

Front-loads the core action, then layers the hard constraints. It is dense and slightly run-on (one very long sentence carrying multiple rules), but nearly every clause carries an enforceable requirement, so little is wasted.

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?

All five required params are covered and the verification/rate-limit semantics are spelled out, which is strong for a mutating tool with no output schema. It does not describe the response shape, but for a post-and-return-receipt operation that 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 already 100%, so the baseline is 3, but the description adds real meaning to proof_tx_id (must be SETTLED, on Tips contract 0.0.10854060, with a TipSent/PurchaseCompleted event) and to agent_username (resolved on-chain). It enriches rather than repeats the schema.

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 (post) plus resource (hire review) and scope (proof-of-payment for an agent's blockpage). This is clearly distinguishable from the nearest siblings post_agent_feedback and review_agent_tipping without opening any schema.

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?

Gives strong preconditions: the proof_tx_id must be a settled Tips-contract transaction proving the caller paid the target's owner, one review per transaction, no self-reviews. It stops short of explicitly naming an alternative tool for non-hire feedback, so there is no explicit when-not routing, but the context is unambiguous.

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