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

With no annotations, the description carries the full burden, and it does disclose concretely what the call produces: cryptographic proofs, a Sourcify exact_match verification result, and settled transaction hashes against a fixed contract address. It omits the rest of the behavioral profile — that this is a read-only lookup, what happens on mismatch or failure, latency/rate characteristics, and that the target contract is hardcoded so the caller cannot vary it.

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 English text is front-loaded and efficient, but the same content is restated in Spanish and Chinese, roughly tripling length with no added technical detail; the Chinese version also truncates the address to '0xd4f77bf8...0a5e', which is less precise. Useful for localization, wasteful as agent-facing specification.

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?

There is no output schema and no annotations, so the description is the only source for what comes back, and it names the three artifact types at a high level. It is still thin on the shape of the response and on failure semantics (e.g., what a non-exact_match result looks like), which matters when an agent must decide whether verification passed.

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?

The input schema takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description is consistent in implying a parameterless lookup, though it never explicitly confirms that the contract is fixed.

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 English sentence states a specific verb and resource ('Return ... cryptographic proofs, Sourcify exact_match verification & settled tx hashes') tied to a named contract (TrustGateEscrow8183 on Base Mainnet), so an agent knows it retrieves on-chain verification artifacts. It does not, however, contrast itself with siblings such as audit_smart_contract_escrow, so the boundary between 'verify status' and 'audit' is left to inference.

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?

The description says only what is returned; it never states when an agent should call this rather than one of the many audit_* escrow siblings, nor any prerequisites or exclusions. Usage is at best inferable from the name, so there is effectively no routing guidance.

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