Create Ci

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without mentioning the required 'name' field, default class_name, validation behavior, or response format, leaving significant uncertainty for a create operation.

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 extremely brief, which is concise, but it under-delivers by merely expanding the acronym 'Ci' to 'configuration item.' It is not a tautology, yet it lacks the richer context that a truly helpful concise description would provide.

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?

The tool has a nested data object and an output schema, but the description only states the high-level purpose. It does not cover essential context such as the mandatory name attribute, default class_value, return values, or how it differs from other create tools, making it incomplete for effective use.

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?

Both parameters have descriptions in the schema (data requires 'name', class_name has a default), giving 100% schema coverage. The description adds no additional parameter semantics, so it meets the baseline of 3 without going beyond the schema.

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 provides a specific verb ('Create') and resource ('CMDB configuration item'), which clearly indicates the tool's function and distinguishes it from generic record creation. However, it does not explicitly reference sibling alternatives, so it is not a perfect 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?

The description gives no guidance on when to use this tool versus alternatives such as create_record or create_update_set. It lacks context, exclusions, or prerequisites, leaving the agent without direction on tool selection.

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