eudr_issue_eip712_attestation

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

With no annotations, the description carries the full burden, but it does disclose real behavioral substance: the exact signed payload (jobId, deliverableHash, riskScore, verdict, expiresAt, v, r, s), the oracle role, and the supported chains. It still omits whether issuance is off-chain signing only or triggers an on-chain write, required permissions/keys, and idempotency or replay behavior.

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 front-loaded sentence with no filler; the action comes first and the payload/chains detail follows. The dense parenthetical field list is informative but slightly reduces readability.

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 5-parameter, no-annotation, no-output-schema tool, the description covers what is produced but not the invocation context: no preconditions, no note on whether a signed artifact must be submitted elsewhere, and no hints about verdict/expiry semantics. Adequate but with clear gaps.

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%, so the schema already documents all five parameters with types, defaults, and ranges. The description's parenthetical field list loosely mirrors some of them (jobId, deliverableHash, riskScore) but adds no syntax, format, or constraint 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 ('Issues') and resource (EIP-712 cryptographic attestation), and enumerates the signed payload fields plus the target contracts/chains, so the agent knows this produces a signature rather than verifying one. It implicitly contrasts with the sibling eudr_verify_eip712_attestation but never names it.

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?

No when-to-use guidance, no prerequisites, and no explicit alternatives or exclusions. The reader can infer this is the issuance counterpart to verification, but nothing in the text states the conditions that select this tool over eudr_verify_eip712_attestation or the escrow lifecycle siblings.

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