List Jedox Databases

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral detail: default hiding of system databases and the option to include them via 'include_system' parameter. It also specifies the return format (array of objects with specific fields). No contradiction with annotations.

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 concise (6 sentences) and front-loaded with purpose. Each sentence serves a clear function: purpose, return info, usage advice, default behavior, return format, and example. No 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?

Given the simple tool (one optional param) and rich annotations, the description covers all aspects: purpose, usage, behavioral nuance, parameter semantics, and return structure. It also provides an example of how to use the output, making it complete for agent invocation.

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% with a well-described 'include_system' parameter. The description reinforces its effect ('Set include_system=true to see them'), adding context about system databases beyond the schema's basic description.

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 'List all databases (models) in the Jedox instance' with specific verb and resource. It distinguishes from sibling list tools by emphasizing the returned 'id' field for subsequent operations and explicitly mentions using it to find database_id before jedox_list_dimensions.

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 context for usage: it should be used first to obtain database IDs for subsequent operations. It also explains the default behavior of hiding system databases and how to include them. However, it does not explicitly contrast with sibling tools or state when not to use it.

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