claim_craft

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

No annotations are provided, so the description carries full burden. It discloses that claiming requires a session, that a no-op occurs if nothing matured but a process exists, that claiming without a craft process is an error, and that a fully-claimed process frees a slot.

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?

The description is 5 sentences, each adding value. It front-loads the main action. While slightly lengthy, it remains clear and informative without redundancy.

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 the complexity of claiming craft batches, the description covers prerequisites, error cases, no-op behavior, and slot freeing. No output schema exists, but the description adequately explains the tool's behavior.

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% with a clear description for tokenId. The description adds context about the cell being owned and the claim conditions, going beyond the schema's simple 'tokenId of the cell whose craft processes to act on.'

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 'Bank every matured craft batch on a cell you own into its resource balance.' It uses a specific verb (claim) and resource (craft batches on a cell), and the tool is well-distinguished from siblings like 'craft' and 'get_craft_status'.

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 explicitly states prerequisites (requires session, call authenticate first), conditions for no-op and error, and suggests using get_craft_status first. It does not explicitly list alternatives but provides sufficient context.

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