Import clauses

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 states that imports can be added or replaced, that some may be skipped or blocked by the free clause cap, and it describes the exact return information (counts plus new library total). This gives the agent meaningful awareness of side effects and outcomes beyond a simple one-line summary.

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 sentences with no wasted words. The first sentence states the purpose and scope; the second sentence describes the return value. The most important behavioral outcome, bulk-loading from file, is front-loaded.

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's purpose, source format, overwrite option, and return metrics are all covered either in the description or the parameter descriptions. Since there is no output schema, the description appropriately discloses the return payload. No critical missing information prevents an agent from calling it correctly.

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%, and both node parameters are already thoroughly documented in the schema. The description adds no additional parameter semantics because the schema already explains path formats, JSON Pro restriction, overwrite behavior, and the free clause cap. Baseline 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 uses a specific verb ('bulk-load') with a clear resource ('clauses into the library') and source ('markdown or JSON file'). This clearly distinguishes it from single-clause tools like clause_add and export tools like clause_export.

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 opening phrase 'Call this tool to bulk-load' clearly identifies the intended use case. It signals that this is for batch importing rather than individual clause operations, and the sibling list reinforces the contrast with clause_add. It does not explicitly exclude alternatives, but the intended scenario is clear.

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