device_create

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

Annotations already indicate this is a mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds useful context that key/session provisioning is not part of creation and must happen afterward, but it does not disclose other behaviors like validation, defaults, or failure conditions.

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 short sentences with no filler. The primary action is front-loaded, and the follow-up routing sentence earns its place by preventing misuse.

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 10 parameters and zero schema descriptions, the description is too thin. It does not explain how to obtain application_id or device_profile_id, what values are expected for dev_eui, or the significance of optional fields, leaving important context to inference.

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 0%, and the description names none of the 10 parameters. It does not explain required identifiers, the meaning of skip_fcnt_check, or how tags/variables are used, so the agent receives no parameter-level guidance beyond raw property names.

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 opens with 'Create a device,' stating a specific verb and resource. It further distinguishes this creation action from downstream provisioning by directing the agent to device_set_keys and device_activate, so it is not confused with those sibling tools.

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 gives clear sequential guidance: use this tool to create the device, then use device_set_keys for OTAA or device_activate for ABP. It does not explicitly state exclusions such as 'use device_update for modifications,' but the create-vs-configure context is clear enough for selection.

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