existdb_list_collection

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

The description gives a clear read-only indication via 'Lists' and specifies the returned metadata, but does not mention authentication requirements, error behavior, or explicitly state that it has no side effects. With no annotations, this leaves some behavioral uncertainty.

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 a single, front-loaded sentence that conveys the essential action and return details without unnecessary words.

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?

While the description clearly explains the tool's main purpose and output, it lacks essential context about authentication parameters (username/password), the meaning of 'endpoint', and prerequisites, making it incomplete for a 4-parameter tool with no annotations or 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?

Only the 'path' parameter has a description in the schema; the tool description adds no information about 'endpoint', 'username', or 'password'. Since schema coverage is only 25%, the description fails to compensate for the undocumented parameters.

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 the action ('Lists the contents of an eXist-db collection') and specifies the output (sub-collections and XML documents with metadata), distinguishing it from sibling tools that handle functions, queries, or single documents.

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?

No guidance is provided on when to use this tool versus alternatives; the description only states what it does without mentioning any exclusions or alternative tools for related tasks.

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