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 and discloses almost nothing: no indication of read-only vs mutating behavior, no auth/payment requirements, no output format, and no rate or size limitations for AI analysis.

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?

One short, front-loaded sentence with no filler, which is efficient. But the 'AI Contract:' prefix merely restates the tool name and the sentence is too thin to be genuinely concise-but-complete.

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 two-parameter tool with no annotations, no output schema, and ambiguous inputs, the description should explain expected input, what the analysis returns, and how it differs from adjacent contract tools. None of that is present.

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%, which sets a baseline of 3 even though the description adds no parameter detail. The schema's own descriptions ('Text to process', 'Contract to process') are tautological and the description does nothing to resolve the ambiguity between the two overlapping inputs, so no uplift is warranted.

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 verb (analyze) and a resource (smart contract), so the general purpose is discernible. However, it does not distinguish this tool from closely named siblings such as x402-smart-contract-audit, x402-contract-scan, and x402-contract-triage, leaving the agent unsure what kind of analysis is performed.

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?

There is no statement of when to use this tool, no prerequisites, and no mention of alternatives. With a sibling set containing multiple contract-analysis tools, the absence of routing guidance is a real gap.

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