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

No annotations are provided, so the description carries the full behavioral burden. It does disclose 'Read-only' and indicates the response content (verdict plus decoded breaching transactions), which is useful. However, it omits auth/prerequisite requirements and any note on whether calling the deprecated alias still behaves identically to the replacement.

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 deprecation notice is front-loaded and the whole description is short, with only a small amount of leftover docstring formatting in the Args block. Every sentence carries information; nothing is padded.

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, so return values need not be explained (though they partially are). With the deprecation routing, read-only disclosure, and parameter format guidance all present, the definition is nearly complete for a simple one-parameter read tool; only auth expectations are unaddressed.

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 0% and the schema documents 'agent' only as a bare string, so the description must compensate. It does: 'public agent identifier (address / DID / ERC-8004 ref)' gives concrete accepted formats that the schema lacks, which is meaningful guidance for the single required parameter.

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 states the tool is a deprecated alias of molcheck_evidence and summarizes its payload ('verdict plus the decoded transactions that breached the mandate'), which is specific about the resource returned. It distinguishes itself from the sibling molcheck_evidence by naming it directly. It loses a point only because its own purpose is defined entirely by reference to another tool rather than standing alone.

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 explicitly says 'Deprecated alias of molcheck_evidence; use that name' — a direct when/when-not instruction that routes the agent to the correct alternative. There is no ambiguity about whether this tool should be selected.

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