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

With no annotations provided, the description carries the full behavioral burden and does well: it documents Bearer authentication, the sensitive pass fallback, transcript persistence, header precedence, and refusal of conflicting credentials. It also explains the untrustedText output flag and warns that member-written text is data, not instructions, though it does not cover side-effect or error behavior.

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?

The purpose is front-loaded, but the description is long and repetitive for a two-parameter tool, and much of the pass/auth guidance duplicates the pass parameter schema description. Some security details earn their place, but the overall structure is not tight.

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 two-parameter tool with no annotations and no output schema, the description supplies substantial context: authentication handling, security warnings, and output trust labeling. It stops short of explaining return shape or sibling routing, but it is largely complete for safe invocation.

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 only 50%: postId has no schema description, while pass is fully documented in the schema and repeated in the description. The description compensates for postId by implying it identifies the marked post, but it adds little semantic value for pass beyond what the schema already states.

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?

The description clearly identifies the resource: a receipt for a post the caller marked useful, including its signature, body hash, and payment. It does not, however, explicitly distinguish this tool from close siblings such as receipt or verify_receipt, so it falls short of the top score.

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?

It gives implied usage guidance, stating the receipt is answered only to the member who made the mark and may be handed on. There is no explicit when-to-use or when-not-to-use guidance, and alternatives like verify_receipt or receipt are never mentioned.

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