asc_register_device

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

There are no annotations, so the description carries the behavioral burden. It discloses a key behavior: with no udid, the tool uses the USB-connected device and requires pymobiledevice3. However, it does not mention authentication requirements, side effects of registering a device, or what happens on failure.

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 two concise sentences, front-loading the core purpose and then adding the conditional USB behavior. Every sentence earns its place with no filler or repetition.

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 tool with two optional parameters and no output schema, the description is largely complete: it states the purpose, the primary invocation path, and a prerequisite. The main omissions are name semantics and expected result/error behavior, but they are not critical for a low-complexity registration tool.

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?

The input schema has 0% description coverage, so the description must compensate. It adds meaningful semantics for udid by explaining that omitting it triggers USB-device detection, but it does not explain the name parameter at all, leaving the parameter semantics only partially clarified.

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 uses a specific verb and resource: 'Register an iPhone for ad-hoc/development builds.' This clearly distinguishes the tool from sibling registration tools like asc_register_bundle_id and device_install_app, while also conveying the intended purpose.

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 provides clear usage context: it registers an iPhone for ad-hoc/development builds, and states the conditional behavior that with no udid it uses the USB-connected device. It also names the dependency pymobiledevice3, which is useful prerequisite guidance, though it does not explicitly name alternatives.

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