import_cmdb_data

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior. The description adds useful context with 'safe field allowlist' and the '[CMDB Write]' tag, but it does not explain upsert semantics, duplicate handling, error behavior, or batch limits for a bulk write 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 compact and front-loaded: one core sentence plus a clear write-operation tag. There is no filler or repetition.

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 bulk CMDB write operation with no output schema, the description is too sparse. It does not explain return behavior, whether existing CIs are updated or skipped, how the allowlist constrains input, or what errors/permissions may be involved.

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 coverage is 100%, so both required parameters are documented in the input schema with clear meanings. The description adds no further detail about the table or data record structure beyond what the schema already provides.

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 and resource: importing CI data into CMDB CI classes. The 'safe field allowlist' phrase adds scope, but the description does not explicitly distinguish this from related import tools such as import_excel_to_import_set or create_import_set_row.

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?

Describes what the tool does but gives no guidance on when to use it instead of sibling import/CMDB tools. There are no prerequisites, exclusions, or alternative selections mentioned.

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