openwisp_create_device

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

No annotations provided, so the description carries the full behavioral burden. It states the operation is a POST (mutating), but does not mention auth requirements, idempotency (MAC uniqueness), what happens on duplicate MAC, or success/return semantics. For a creation tool with zero annotation coverage, this is a notable gap.

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?

Two compact sentences: a category tag, a specific action, and the HTTP endpoint. No filler, front-loaded action verb. Every clause earns its place.

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?

A mutation tool with no annotations, no output schema, and no behavioral detail. It does not explain return values, prerequisite resources (e.g., organization must exist), or authorization. For a 5-parameter device-creation tool, the description is too thin.

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%, so baseline is 3. The description adds no parameter-level meaning beyond the schema, but all five parameters already have clear descriptions (examples for mac, name, model; default for system).

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?

Specific verb+resource: 'Register a new network device in OpenWISP Controller.' Distinguishes from siblings like update_device, delete_device, list_devices by the 'create' verb, and the HTTP POST line reinforces creation. Lacks explicit sibling differentiation, which caps it below 5.

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?

No when-to-use guidance, no prerequisites (e.g., requires org exists, requires token), no statement of when to use this vs. openwisp_activate_device or openwisp_create_device_connection. The category tag and endpoint are the only context.

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