existdb_list_namespace_functions

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

No annotations are provided, so the description carries the burden. It discloses that only documented functions are listed (a filtering behavior) and implies a read-only operation. However, it does not explicitly state side-effect-free behavior, error scenarios, or any limitations beyond 'documented'.

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 two sentences, front-loads the core action, and then gives concrete input examples. Every word adds value, with no redundant or vague phrasing.

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 simple single-parameter list tool, the description sufficiently explains the purpose and input format. It does not describe the return value format, but the tool name and description ('Lists all documented functions') imply the output is a list, so it is largely complete. A small gap: no mention of what happens for an unknown/invalid namespace.

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?

The input schema already has 100% coverage with a clear description and examples. The tool description adds the phrase 'conventional prefix' and more prefix examples, but these largely overlap with the schema. It does not add significant new meaning beyond what the schema provides.

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 tool lists all documented functions in a specified eXist-db / XQuery namespace. It uses a specific verb ('Lists') and resource ('documented functions in a given namespace'), which distinguishes it from siblings like existdb_list_namespaces or existdb_lookup_function.

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 provides clear context on when to use this tool: when you need a full list of functions in a namespace. It gives examples of valid inputs ('xmldb', 'ft', 'util', 'sm', 'fn'), but it does not explicitly mention alternatives or exclusions such as 'use existdb_lookup_function to search for a specific function'.

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