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

Beyond the readOnlyHint=false write profile already in annotations, the description discloses that no network, fetch, money movement or external write occurs, states the x402 price of 0.10 USDC per call plus the 10 free calls per rolling 30 days, and specifies the X-Wever-Wallet-Proof binding requirement. It also states what the returned signed report contains and that it carries an Ed25519 receipt. This is exactly the context annotations cannot convey.

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 key scoping statement and the sibling pointer are front-loaded and almost every clause carries operational information. The opening sentence is a dense run-on that compresses triggers, owners, action classes and escalation logic into one block, which slightly hurts first-pass scanability, and the marketing footer links are marginal.

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?

With no output schema, the description still tells the agent what comes back (checked findings with fixes, a verdict of judgment_based/partly_operable/operable, a signed receipt), what it costs, and how to authenticate. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the semantic role of trigger fields (trigger as written OR metric/operator/value/window, each with action class, owner, response time and escalation), which tells the agent how the pieces relate. It stops short of naming individual field constraints, but the schema already handles those.

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 names a concrete verb and artifact ("submit an escalation policy") and scopes it to the case where something is already going wrong, then explicitly distinguishes it from the sibling wever_action-threshold-check, which covers approval before acting. An agent can pick between the two without opening either 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 states when to use it (an existing incident's escalation policy) and names the alternative plus the condition that selects that alternative ("Approval before acting is wever_action-threshold-check"). The preconditions — signed wallet proof, paid call — are also spelled out.

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