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

Annotations already declare readOnlyHint and destructiveHint=false, but the description goes far beyond them: GET with no redirects and public DNS only, 512 KB cap, no account access or money movement, a 0.10 USDC x402 charge with 10 free signed-wallet calls per rolling 30 days, and an X-Wever-Wallet-Proof binding to the exact JSON arguments and route. It also discloses that the return is an Ed25519 signed receipt and asserts the report only matches words/figures/dates without interpreting meaning. That is unusually complete behavioral disclosure for a paid, open-world tool.

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?

Core purpose is front-loaded, but the description is padded with payment-rail detail, a contract path, and a marketing URL that could be condensed. It also carries a sentence apparently copied from a two-text comparison tool ("matches words, figures, dates and named items between the submitted texts") that contradicts the single-text input and forces the reader to reconcile it.

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?

No output schema exists, and the description does adequately sketch the return: counts and short quotes of version mentions, flagged deprecated endpoints/parameters/functions, and a signed receipt. Input handling, cost, and auth binding are all covered. Minor gaps remain around report format and pagination/size of the quoted output, plus the internally inconsistent comparison sentence.

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%, so text, url, format, and current_version are already documented in the schema, including the format default heuristic. The description adds only the either/or constraint and the version-number concept, which the schema's oneOf and pattern already enforce. Baseline 3 is appropriate since the schema carries the parameter burden.

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 opening states a specific action: submit documentation (text or public HTTPS url) plus a current_version and receive a signed report on older/newer version mentions and self-marked deprecations. That is a concrete verb-plus-resource, well beyond a restatement of the name. It loses a point because it never distinguishes itself from near-identical siblings such as wever_api-change-check, wever_changelog-check, or wever_contract-diff-check, and the later sentence about matching "between the submitted texts" muddies what is actually compared.

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?

There is no explicit when-to-use guidance and no named alternative, despite a large sibling family of *-evidence-check and change/diff tools that an agent must choose between. The only guidance is mechanical (one of text or url, public HTTPS, 512 KB). An agent must infer from the name alone that this is for checking docs against a target version rather than for API diffs or changelogs.

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