Edtb Cf Artifact

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does this well by stating that it uses 1cv8 DESIGNER, reads infobase parameters from EDTB_INFOBASE_PATH, operates on a file infobase, runs non-interactively, and enforces a timeout. It does not explicitly warn that 'load' may overwrite existing data, but the load action is clearly described as writing a file into the infobase.

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 compact and well-structured: a one-line statement of purpose, then explicit dump/load semantics, then execution constraints. Every sentence adds useful information, and there is no filler or tautological restatement of the tool name.

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 two-mode artifact tool, the description covers the purpose, both actions, the file/infobase relationship, the external command, the relevant environment variable, and the non-interactive/timeout behavior. The main gaps are the undocumented 'projectPath' parameter and the lack of an explicit overwrite warning for load, but an output schema exists, so return-value details are not required here.

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 0%, so the description must compensate. It usefully defines the 'action' values and clarifies that 'path' is a file path. However, the optional 'projectPath' parameter is not explained at all, leaving one of three parameters semantically undocumented.

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 identifies a concrete resource (.cf/.cfe artifact) and a clear verb pair (dump/load), then defines the two action modes explicitly. This makes its role distinct from sibling tools focused on mxl, forms, panels, or mutations.

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?

Usage is implied by the dump/load semantics: an agent can infer that this tool is for exchanging .cf/.cfe artifacts with an infobase. However, there is no explicit statement of when to prefer this tool over alternatives, no exclusions, and no when-not-to-use guidance.

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