reveal

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

No annotations provided, so description carries full burden. It comprehensively discloses: authentication requirement, free first reveal, re-reveal restrictions, auto-approval of CPU, on-chain submission, confirmation wait, transaction hash output, and delay for resource application. 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?

Description is longer than necessary but every sentence adds value. Front-loaded with purpose. Could be trimmed slightly but remains clear and well-structured.

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?

For a complex tool involving on-chain transactions and delayed effects, the description covers prerequisites, phases, restrictions, side effects, and how to read results. No output schema, but transaction hash is mentioned. Complete given the context.

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% and already describes tokenId as 'The tokenId of a cell you own to reveal.' Description adds 'Land cell' but provides no additional semantic value beyond the schema.

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 reveals resource deposits of a Land cell the user owns. It distinguishes from siblings by detailing the unique reveal mechanism (first free, re-reveal allowed only after depletion) and directs to get_cell for reading results.

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 states prerequisite: requires session and call to authenticate. Provides usage scenarios: first reveal free, re-reveal allowed only after full depletion. Mentions auto-approval of CPU cost and on-chain transaction. Guides to read results with get_cell.

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