existdb_create_collection

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention authentication requirements (endpoint, username, password are in the schema but not described), behavior if the collection already exists, error conditions, or return values. The only behavioral hint is that the parent must pre-exist.

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 one concise sentence with no redundant details. It directly states the operation with no filler, making it easy to parse quickly.

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?

With 5 parameters (3 without schema descriptions), no annotations, and no output schema, the description is not complete enough. It omits authentication requirements, error behavior, and return semantics, which are critical for an agent to invoke the tool 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 only 40% (name and parent have descriptions). The description adds that the parent is existing and the new item is a sub-collection, but it says nothing about the endpoint, username, or password parameters, leaving them completely undocumented. It does not sufficiently compensate for the low schema coverage.

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 states a specific action (creates) and a specific resource (a new sub-collection inside an existing eXist-db collection). This clearly distinguishes it from sibling tools like existdb_list_collection or existdb_get_document, which perform different operations.

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 phrase 'inside an existing eXist-db collection' implies a prerequisite: the parent collection must already exist. However, it does not explicitly guide when to use this tool versus alternatives (e.g., creating a collection vs. storing a document), nor does it mention any exclusions or alternative tool names.

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