eudr_verify_eip712_attestation

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

No annotations exist, so the description carries the full burden. It does disclose the validation facets and the resulting recommended action (COMPLETE_JOB or SLASH_JOB), which is meaningful behavioral context, but it never states that the call is side-effect-free, what happens on a failed signature, or whether any auth/key material is required.

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?

A single well-formed sentence that leads with the verb and resource and front-loads the checks performed. Dense but no wasted clauses; only slightly overstuffed with parenthetical outcome values.

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 no output schema and no annotations, the description partly compensates by naming what is validated and the two possible recommended actions, giving the agent return-value context. It is nearly complete for a one-parameter verification tool, though side-effect and failure-mode behavior remain unstated.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents the attestation object (v, r, s signatures). The description adds no format or structural detail beyond what the schema provides, matching the baseline for high coverage.

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 (cryptographically verifies) plus the exact resource (EIP-712 EscrowAttestation proof) and the checks performed (signature validity, expiration). This clearly distinguishes it from the sibling eudr_issue_eip712_attestation, which creates rather than validates attestations.

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?

Usage is only implied: an agent can infer this is called to validate an attestation before acting on COMPLETE_JOB/SLASH_JOB, but the description never states a trigger condition, prerequisites, or when to prefer it over related verification siblings.

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