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

No annotations exist, so the description carries the full behavioral burden. It never states that this is a read-only/compute operation, whether anything is persisted or registered, what happens if the address is invalid or absent, or how costly/long the audit is. 'Audit' implies read semantics, but that is inference, not disclosure.

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?

Two tight sentences with no filler; the operation is front-loaded and the usage cue follows immediately. Nothing to trim.

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 means the description needn't describe the verdict payload, and the when-to-use cue is present. But with no annotations and partial schema coverage, it leaves gaps around read/write semantics, the meaning of 'agents', and chain defaults that an agent would want.

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 only 67%, and the description adds nothing about any parameter. 'Safe/address' loosely echoes the address param, but chain, the enum values, and 'comma-separated agent keys' are left entirely to the schema. With a moderate coverage gap and zero compensating detail, this is below baseline.

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?

Specifies a concrete verb and resource: run a provenance audit on a Safe/address. It reads clearly apart from the get_* siblings, though it never names an alternative tool or distinguishes itself from passport/alert lookups explicitly.

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 real trigger condition ('is this fake?') and the intent behind it (shareable verdict), which is more than most siblings offer. It lacks any exclusion or routing to related tools, so it stops short of a 5.

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