domainLock

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

With no annotations, the description carries the behavioral disclosure burden. It reveals the security effect of locking, but does not mention reversibility, permissions, side effects on pending transfers, or response format. This is minimal but not misleading.

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?

One concise sentence with no filler; the action and purpose are front-loaded. The link to API reference is an optional extra and does not detract.

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?

Adequate for a one-parameter, low-complexity tool, but it omits practical context such as expected output, error conditions, and whether the lock is reversible or requires special permissions. The agent can call it correctly but with limited surrounding knowledge.

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 description coverage is 100% for the single 'domain' parameter, so the schema carries the parametric meaning. The description adds no further detail about domain format or constraints, matching the baseline.

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 action ('Lock a domain') and its intended outcome ('prevent unauthorized transfer'), clearly distinguishing it from sibling operations such as domainUnlock. The verb and resource are explicit.

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 purpose phrase implies when to use it (when transfer protection is needed), but it does not explicitly mention alternatives or exclusions. There is no direct contrast with domainUnlock or other domain-management siblings.

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