import_cmdb_data

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

Annotations indicate readOnlyHint=false (write) and openWorldHint=true (side effects). Description adds '[Write]' but fails to disclose potential impacts like overwriting existing records, triggering business rules, or creating update set entries. This is insufficient for a write operation with side effect potential.

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 efficient with a single sentence and a tag, front-loading the key action. However, it could benefit from a brief note on expected return or error handling.

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?

Given the complexity of an import operation with no output schema, the description is adequate but lacks details on data format requirements, allowed table values, and error behavior. Schema covers basics, but more context would help.

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 clear descriptions for 'data' and 'table'. The description does not add additional meaning beyond what the schema provides. Baseline score of 3 applies.

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 clearly states 'Import CI data into CMDB via import set' with a specific verb and resource. It distinguishes from sibling tools like create_ci_relationship or cmdb_reconcile by focusing on import set mechanism.

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 implies usage for importing CI data but does not explicitly specify when to use this tool versus alternatives like create_record or create_incident. No when-not-to-use or exclusion criteria are provided.

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