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

Beyond the annotations' safety profile, the description discloses the cost (0.10 USDC per call on Base via x402 exact), the 10 free signed-wallet calls per rolling 30 days, the X-Wever-Wallet-Proof binding requirement, the Ed25519 signed receipt, and the crucial behavioral caveat that the report only matches words, figures, dates and named items rather than interpreting meaning. That last point materially changes how an agent should treat the output and is not derivable from any structured field.

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 output shape is front-loaded before the operational details, and most sentences earn their place (cost, proof binding, receipt, matching caveat). It is dense but long, and the contract/human-page URLs plus the repeated payment framing push it slightly past what a caller strictly needs.

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?

There is no output schema, and the description compensates fully by describing the brief's contents and the signed receipt. For a paid, non-idempotent call, it also supplies the cost, auth binding, and data-access boundaries an agent needs to invoke it safely.

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 the schema already defines text, label, and format, including the format enum's default heuristic. The description adds no syntax or semantic detail beyond what the schema states. Baseline 3 applies when 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 description uses a specific verb and resource ("submit meeting notes or a transcript excerpt" into a "signed brief") and enumerates exactly what the artifact contains: participants, decisions, owned/due action items, open questions, and the flagging of unowned or undated action items. That output shape distinguishes it from sibling brief tools such as wever_contract-brief or wever_agent-daily-operator-brief 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?

It makes clear the input context (meeting notes or transcript) and states scope limits ("reads only the material in the call"), plus the payment model and free-tier allowance an agent needs before calling. It never names an alternative tool or a when-not condition, so an agent choosing between this and, say, wever_diligenceops-paid-run must infer the choice.

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