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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently explains the payment model (x402 on Base, $0.02–$0.03 USDC), reuse mechanics, and optional claim checking. However, it does not describe error behavior (e.g., inaccessible pages), the structure of the output artifact, or how the optional claim check is triggered (no parameter for that). These gaps reduce transparency.

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 description is a single paragraph of about 150 words, with every sentence adding value: main purpose, optional feature, reuse, pricing, and sharing. It is front-loaded with the primary action. While efficient, it could be more scannable with bullet points or shorter sentences, hence not a perfect 5.

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?

The tool has no output schema, so the description must explain return values. It mentions 'bounded, LLM-ready Markdown with a content-addressed artifact' but does not specify the artifact's format, how to re-verify, or what the optional claim check returns. The pricing and reuse details are helpful, but the lack of output clarity leaves the agent with insufficient information to use the tool correctly.

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 100%—both 'url' and 'wallet' are already fully described in the input schema. The tool description adds no additional meaning or constraints beyond what the schema provides. According to the rubric, when coverage is high, the baseline is 3, and the description does not exceed that.

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 states the tool converts a public web page into 'bounded, LLM-ready Markdown' with a content-addressed artifact for verification. It uses specific verbs ('Turn', 'compile') and resource ('public web page'), and distinguishes from siblings by emphasizing the re-verification and payment reuse features, which are unique among the listed sibling tools.

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?

The description implies when to use the tool (to get a verified, reusable Markdown version of a page) but does not explicitly state when not to use it or compare it to alternatives. It mentions the cost and reuse benefits but lacks direct guidance on distinguishing from similar tools like 'evidence_artifact' or 'tereno_find_claims'.

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