openwisp_create_device_connection

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutating POST and discloses the endpoint, but says nothing about required permissions, whether the device must already be registered, idempotency/duplicate handling, or what the response contains.

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?

A single tight sentence with the action front-loaded, followed by the endpoint parenthetical. Nothing is wasted, though the endpoint boilerplate is low-value padding.

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 creation tool with no annotations, no output schema, and no explanation of what a device 'connection' represents or what happens on success, the description is too thin. The schema covers the inputs adequately, but the behavioral side is left entirely unaddressed.

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%, with 'id', 'name', and 'credential' each documented in the schema, so the schema does the heavy lifting. The description adds no meaning beyond the schema (e.g. that 'credential' is optional or what formats are accepted), which is the baseline expectation here.

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 verb ('Create') and resource ('connection for a device'), and the naming plus the category tag readily distinguish it from openwisp_list_device_connections, openwisp_get_device_connection, and the update/patch/delete siblings. It stops short of explicitly routing the agent versus those siblings, so it is clear but not maximally differentiating.

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?

There is no guidance on when to create a connection versus updating an existing one, no prerequisites (e.g. device must be registered, credential must exist), and no mention of alternatives. The endpoint path is the only operational context.

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