Create Units

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

No annotations are provided, and the description discloses no behavioral information: no mention of side effects, required permissions, idempotency, or response behavior. 'Create One' gives an agent no understanding of what happens when the tool is invoked.

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 words is not conciseness; it is under-specification. The description provides no structure, context, or useful content, and it fails to earn its place as a meaningful tool definition.

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 13 parameters, no annotations, and no parameter descriptions, 'Create One' is grossly incomplete. The presence of an output schema does not compensate for the absence of any operational or semantic guidance.

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?

There are 13 parameters with 0% schema description coverage, and the description adds no meaning to any of them. Even the required 'name' parameter is left completely unexplained despite being the only required field.

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 'Create One' is essentially a singular restatement of the title and tool name; it does not explicitly name the resource (units) or provide any distinguishing detail. An agent would have to infer the purpose entirely from the tool name, and the description offers no differentiation from similar create 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?

There is no guidance on when to use this tool versus alternatives like update_units_merge or delete_units_by_item. No context, prerequisites, or exclusion criteria are provided, so an agent cannot make an informed routing decision.

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