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

Annotations already cover readOnly/idempotent/openWorld, but the description adds genuine behavioral context: modules can move funds via execTransactionFromModule with no owner signatures, the possible verdict values, and the auth/pricing model ($0.04 via x402, prepaid x-credit-token header, no API key, no free tier). That is exactly the extra layer annotations cannot express.

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 hook and risk explanation are front-loaded effectively, but the text repeats the required input ('address= required' and again 'Required input: address'), and marketing flourishes ('critically', 'Not financial advice') dilute an otherwise tight description.

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?

An output schema exists and the description still names the verdict values, so an agent has everything needed: input, semantics, risk interpretation, and cost/auth. Nothing material is missing for a single-param read tool.

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?

Only one parameter and schema description coverage is 100%, so the baseline is 3. The description restates 'address= required' twice but adds no syntax, format, or resolution detail beyond what the schema already provides.

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 the exact verb+resource: given an address, determine whether it is a Gnosis Safe and report owners, M-of-N threshold, version, activity, and enabled modules, plus a multisig/single_signer/has_modules verdict. This is clearly distinguishable from siblings like safe_to_send, safe_approve, contract_owner or address_check.

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?

Frames the use case explicitly as 'the counterparty check before you trust funds to a multisig', including the risk model (modules with unilateral control). It gives clear context for when to run it but does not name alternative tools or say when not to use it.

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