nullclear_verify_kya_mandate

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

With no annotations, the description carries the full burden. It usefully discloses the three things verified (mandate existence, active validity, limit compliance), which implies a read-only check, but does not state the read-only nature outright, nor any auth, rate limit, or failure 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?

A single dense sentence that front-loads the resource (KYA mandate) before the verification aspects. No filler, though the three enumerated checks make it slightly run-on.

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, so the description should clarify what the verification returns (pass/fail booleans, reasons, limits). It does not, and with zero annotations the agent also lacks auth and error-handling context, leaving a meaningful gap for a verification tool.

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 both required params (agentId, transactionAmountUsd) and chainId are already documented. The description ties transactionAmountUsd to corporate-limit checking, adding slight meaning, but does not go beyond the schema's own parameter docs — baseline 3 applies.

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 ('Verify') and a well-scoped resource: the agent's KYA corporate liability mandate, its active validity, and whether a transaction amount fits corporate limits. This is clearly distinguishable from a reputation check or escrow call, though it never names the siblings explicitly.

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 intent (verifying a mandate before transacting) is implied but never stated as explicit when-to-use guidance. There are no exclusions or pointers to the sibling tools (check_reputation, escrow_x402_call), so the agent must infer the sequencing itself.

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