build_permit

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

No annotations provided; description only hints at on-chain query for nonce but does not disclose that building a permit is off-chain, does not modify state, or requires signing. Missing critical behavioral context.

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?

Two sentences, no redundant information. Front-loaded with core purpose.

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?

Tool has 5 parameters with no schema descriptions and no output schema. Description omits what the payload looks like, how to use it, and that it requires off-chain signing. Incomplete for a complex standard like EIP-2612.

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 0% and description does not explain any parameter (owner, spender, amount, token, validForSeconds) beyond their names. No guidance on formats, constraints, or meaning.

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?

Description explicitly states 'Build an EIP-2612 permit payload (gasless approval)', clearly defining the action and standard. This distinguishes it from sibling tools like build_token_approve which does on-chain approvals.

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 description mentions a prerequisite ('Requires the token's current nonce') but does not specify when to use this tool vs alternatives like build_token_approve. Usage context is implied but not explicitly clarified.

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