worker_register

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

Discloses that the stake is slashable, that losing a dispute results in slashing, that double registration halts, and specifies asset (BEAM) and units (groth). No annotations provided, so description carries full burden.

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?

Well-structured single paragraph that front-loads purpose and details. Slightly long but efficient; no wasted sentences.

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?

Covers purpose, parameter, asset, consequences, and error handling. Output schema exists, so return info is handled. References sibling tool for pre-check.

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?

With 0% schema coverage, description explains the 'stake' parameter: it is the bond amount in groth, BEAM only. This adds meaning beyond the schema type of integer.

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 posts a worker reputation bond on the Idios contract, explains what the bond is, and differentiates from related tools like view_worker_bond.

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?

Provides context on when to use (to post bond) and advises checking view_worker_bond first to avoid double registration. Could be more explicit about when not to use.

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