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

Annotations already declare readOnly=false, destructive=true, idempotent=true, openWorld=true. The description adds real value beyond these: it explains the no-op dedup path, the auth/enrollment prerequisites, and that gas is required on Base. It does not clarify what 'destructive' means for this tool (on-chain spend, non-reversible attestation), leaving a small gap.

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?

Three tight sentences: what it does, the dedup edge case, then prerequisites last. No filler, and the core action is front-loaded.

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 a no-output-schema, nested-object mutation tool, it covers auth, gas, and idempotent behavior well. It omits what a successful response contains and the effect of expiresIn timing, which an agent might want, but nothing critical 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 description coverage is 100% and all four parameters are documented there (to/level/context/expiresIn with ranges). The description only reinforces that the target may be a wallet or social identity, which the nested schema already says, so it adds little beyond the 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?

The description names a specific verb (Create), resource (unidirectional trust attestation), chain/standard (Base, EAS), and the source/target of the attestation. This clearly separates it from siblings like connect_trust_revoke, connect_trust_check, and connect_trust_graph.

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 gives the operational preconditions explicitly (CONNECT_API_KEY, Smart Send attestation signer enrolled, ETH on Base for gas) and states dedup behavior when an identical attestation exists. It does not explicitly contrast when to prefer this over connect_trust_revoke or connect_trust_check, so it falls 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.