mdb_list_tables

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

No annotations are provided, so the description must carry behavioral disclosure. It usefully exposes the session-state dependency (dynamic session vs pre-configured database), but says nothing about permissions, result format, or whether system schemas are included by default (that only appears in the schema).

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?

Two short sentences, front-loaded with the action, followed by the one operational rule that matters. No filler.

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?

Complete enough for a zero-required-param list tool: it explains the session/config-label duality and the fallback sibling to consult. The only gap is return-shape expectations, which is minor for a listing operation with 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?

Schema description coverage is 100%, so both parameters are already fully documented in the schema, including the session-vs-config-label rule. The description restates that rule rather than adding format examples or edge cases beyond it.

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?

States a specific verb and resource ('List tables in MonetDB'), which is clearly distinct from mdb_list_databases and mdb_list_schemas by resource type. It does not explicitly contrast itself with those siblings, but the resource naming makes the distinction inferable.

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?

Gives a concrete conditional rule for the optional parameter ('omit database if dynamic session active; otherwise pass database="config_label"') and a prerequisite ('call mdb_list_databases first if unsure'). This is strong when-to-use guidance, though it never names the sibling mdb_list_schemas as the alternative for schema-level listing.

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