agent_session

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

Discloses key behaviors: cost ($0.10 USDC per call), output structure, channel flexibility, and validity period. Lacks details on failure modes or rate limits, but is otherwise transparent.

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?

Three sentences, front-loaded with action verb 'Mint', no redundant information. Every sentence adds value.

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?

Given no output schema and few parameters, the description fully explains purpose, inputs, outputs, and when to use it. No apparent 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?

All parameters have schema descriptions (100% coverage), so baseline is 3. Description adds context (EIP-712 verification, single-use, Base mainnet), elevating beyond schema-only 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?

The description clearly states the tool mints an agent session using EIP-712 verification and on-chain attestation on Base mainnet. It specifies the output (single-use 6-digit code, expiration, transaction hash). Sibling tools are unrelated, so no ambiguity.

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?

Explicit guidance: 'Use this when an agent needs to authenticate itself...via voice call or HTTPS handshake.' Includes cost and settlement details, helping distinguish from other tools.

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