request_challenge

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

With no annotations, the description carries the behavioral burden and does well: it discloses that an empty inputs object avoids transmitting private witness inputs, that witness data must stay out of model context/dApp UI/logs, and the server-side consequence of omitting the nonce. It does not spell out whether a challenge is consumed, reused, or expires, so it stops short of full disclosure.

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?

Front-loaded with the purpose and the critical nonce carry-forward, and every sentence contributes routing or safety information. It is slightly dense and repeats the inputs: {} guidance that already appears in the schema, which costs a point.

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?

No output schema exists, so the description usefully names what comes back (nonce, payment offers, optional TEE key) and what must be done with it. It leaves the multi-step flow's other steps implied rather than enumerated, but is sufficient to invoke this tool correctly.

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 coverage is 100%, so the baseline is 3; the description earns above baseline by explaining the special {} sentinel value and its purpose rather than just restating the schema. It does not add format or syntax detail for the circuit argument beyond the schema enum.

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 and resource ("Request a challenge from the server") and anchors itself as step 2 of a flow, so the agent knows exactly what action it performs. It actively distinguishes itself from siblings by naming submit_proof and generate_proof and the conditions that route to them.

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?

Gives explicit usage direction (pass inputs: {} to discover the nonce, offers and TEE key), an explicit constraint on the downstream call (nonce MUST go to submit_proof, otherwise another challenge is issued), and an explicit when-not with alternates (use generate_proof or the SDK for paid/encrypted orchestration).

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