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

No annotations exist, so the description carries the full burden, and it does well: it discloses the asymmetric authorization model, the exact signing inputs, and that changes apply immediately once signed. Missing are reversibility, whether partial rule updates replace or merge, and error behavior on an unsigned weaken attempt.

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?

Dense but front-loaded: the action comes first, then the authorization split, then the unit convention. Capitalized WEAKENING and GOVERN flag the risky path effectively. The parenthetical "(same as passkey in the UI)" is the one sentence that earns less than its space.

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 an unannotated mutation tool with an unspecified nested rule array and no output schema, key information is absent: the expected structure of each rule object, whether rules are replaced wholesale, and what a successful call returns or how failures surface. The authorization model is well covered, but the payload contract is not.

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 67%; challengeId and walletSignature are already described in the schema, and the description only adds the condition "only when weakening rules", which the schema description also states. The most opaque parameter, the free-form array of rule objects with an untyped item schema, gets no explanation of its shape or fields.

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?

States a specific verb and resource: setting cosigner quorum rules across "send + swap USD bands". The send/swap scope and the two-band structure are concrete, and get_cosigner_rules is the obvious read counterpart among siblings. It doesn't explicitly name that sibling, so sibling differentiation is implicit rather than stated.

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?

Gives a clear decision rule distinguishing two modes: tightening needs only the agent key, while weakening (lower required cosigners / raise the amount floor) is a GOVERN action requiring challengeId + walletSignature. It does not point to sibling tools for creating the challenge or listing existing rules, so the surrounding workflow must be inferred.

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