craft

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

No annotations provided, so description carries full burden. Explains inputs debited upfront, most recipes free and immediate timer, forge_wcpu costs and auto-approves allowance, submits on-chain payment, waits for confirmation, timer starts after settlement. No contradictions.

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?

Single paragraph packs dense information, front-loaded with main action. Could benefit from slight structuring (e.g., bullet points), but still concise and informative.

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 tool complexity (multiple recipe types, different behaviors, sibling tools), description covers prerequisites, cost, timing, and result handling. No output schema, but guides to track and claim.

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%, baseline 3. Description adds value: for recipeId, directs to list_recipes for details; for batches, clarifies inputs debited upfront for all. Extra context justifies 4.

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?

Clearly states 'Run a craft recipe on a cell you own'. Identifies the action (run/craft), resource (cell), and distinguishes from siblings by referencing related tools (authenticate, list_recipes, get_craft_status, claim_craft). Also mentions specific recipes like forge_wcpu.

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?

Explicitly tells when to use: requires session, call authenticate first, discover recipes with list_recipes, track progress with get_craft_status, claim with claim_craft. Distinguishes forge_wcpu as special case with cost and payment flow.

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