vbcs_import_bo_data

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description reinforces this with the specific blast radius: 'replace' OVERWRITES the object's existing data, versus append which only adds rows. It also discloses the locking prerequisite. It does not cover auth/permission needs or error behavior, so short of a 5.

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 dense sentences; the destructive 'replace' warning is capitalized and front-loaded, and the locking prerequisite is placed last as the pre-call action. No filler.

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?

No output schema exists, but the description covers the mutation tool's key risks, format constraints, and preconditions, which is enough for correct invocation. Slight gap: nothing on the 'target' parameter's effect or on partial-failure reporting.

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 67%, and the description compensates by explaining the file-name-to-object-id constraint, that boName defaults to the file name and should be omitted for .zip, and by restating the mode semantics with emphasis on replace. The 'target' parameter's design-vs-deployment distinction is only in the schema, not the description.

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 (Import) and resource (business-object data) plus the target environment (standalone VBCS instance), and the accepted file formats. It is clearly distinguishable from sibling vbcs_export_bo_data.

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?

Gives concrete usage conditions (one object per .csv/.xls/.xlsx with file name equal to object id, or a .zip for several) and a prerequisite ('Lock a live app first'), which maps to sibling vbcs_lock_application. No explicit when-not or a named alternative beyond the lock/unlock siblings.

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