Import collections

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does a good job by explicitly warning that deleteMissing deletes collections not present in the import list and adding 'use with caution'. It does not mention atomicity or permission requirements, but the main destructive behavior is surfaced clearly.

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 three sentences with no filler. The main action is front-loaded, the destructive warning follows immediately, and the recommended use case appears at the end. Every sentence earns its place.

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 mutating bulk import with no annotations and no output schema, the description covers the operation, the dangerous side-effect, and the intended use case. It could additionally mention whether existing collections are updated or whether the import is transactional, but the essentials for safe invocation are present.

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 the baseline is 3. The description adds useful context beyond the schema by specifying that collection definitions are 'as exported from the PocketBase admin UI' and by reinforcing the deleteMissing conditional behavior. This is meaningful but not extensive.

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 opens with 'Bulk import collections from an array of collection definitions', which clearly states the verb, resource, and bulk nature of the operation. It also distinguishes itself from per-collection create/update tools by noting this is the recommended way to apply a full schema in one call.

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 explicitly frames the tool as 'the recommended way to apply a full schema in one call', giving a clear use case. It also warns about the destructive behavior of deleteMissing. However, it does not explicitly contrast it with when to use individual collection tools like create_collection or update_collection.

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