import_categories

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

Discloses create/update behavior based on existence but lacks details on error handling, atomicity, or partial failures for the batch array input. With no annotations, the description should provide more behavioral context.

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?

Four concise sentences: purpose, upsert behavior, required fields, optional fields. No unnecessary words, front-loaded with key information.

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?

Covers operation, parameters, and upsert behavior. Lacks return value description (e.g., list of created/updated category IDs) and error scenarios, but adequate for a simple import tool given no output schema.

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?

Input schema has 0% coverage for the array object properties. The description fully compensates by listing required fields (correlationId, name) and optional fields (parentCorrelationId, isPrivate, order), adding essential meaning.

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 or update knowledge base categories' with specific verbs and resource. It distinguishes from sibling tools like 'update_category' by indicating batch upsert behavior. The operation is well-defined.

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 use for batch import/update but does not explicitly state when to prefer this over siblings like 'update_category' or 'list_categories'. No when-not or alternative guidance is provided.

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