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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: the data source is an internal registry and results include 'category hints' and ABI 'availability', signaling these are advisory rather than authoritative. It omits what happens on a miss, but the annotation bar is largely met.

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 short sentences, zero waste: purpose first, return contents second, call timing last. Everything is front-loaded and each sentence earns its place.

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 a rich annotation set, a 100%-covered two-parameter schema, and an output schema that carries return structure, the description is nearly complete. The only gap is behavior on a failed lookup (unknown contract), which an agent would benefit from knowing.

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% and both parameters (chain slug, 0x address) are fully documented in the schema, so the description carries no additional parameter burden. Baseline 3 is appropriate — the description adds no syntax or format detail beyond the schema.

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 ('look up a smart contract in CryptoTaxEdge's registry') and enumerates what comes back (protocol metadata, contract type, ABI availability, label, category hints). The closing clause ties it to the sibling classify_* tools so an agent can tell which one to reach for first.

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?

Explicitly tells the agent to call this before deciding whether to classify a transaction, which is a concrete usage condition relative to classify_transaction/classify_batch. It stops short of stating when not to use it or what to do when the lookup misses, so no exclusion guidance.

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